fix a case where file tracked by git unexpectedly becomes annex pointer file
smudge: When annex.largefiles=anything, files that were already stored in git, and have not been modified could sometimes be converted to being stored in the annex. Changes in 7.20191024 made this more of a problem. This case is now detected and prevented.
This commit is contained in:
parent
b9481c6ba0
commit
ea3cb7d277
10 changed files with 90 additions and 34 deletions
13
doc/todo/git_annex_add_option_to_control_to_where.mdwn
Normal file
13
doc/todo/git_annex_add_option_to_control_to_where.mdwn
Normal file
|
@ -0,0 +1,13 @@
|
|||
Make `git-annex add --annex` and `git-annex add --git` add a specific file to
|
||||
annex or git, bypassing annex.largefiles and all other configuration and state.
|
||||
|
||||
One reason to want this is that it avoids users doing stuff like this:
|
||||
|
||||
git -c annex.largefiles=anything annex add foo.c
|
||||
|
||||
Such a temporary setting of annex.largefiles can be problimatic, as explored in
|
||||
<https://git-annex.branchable.com/bugs/A_case_where_file_tracked_by_git_unexpectedly_becomes_annex_pointer_file/>
|
||||
|
||||
Also, this could also be used to easily switch a file from one storage to
|
||||
the other. I suppose the file would have to be touched first to make git-annex
|
||||
add process it?
|
Loading…
Add table
Add a link
Reference in a new issue