mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

comment

Browse source
This commit is contained in:
Joey Hess 2019-10-22 13:30:04 -04:00
parent df963469f2
commit 5581dc3318
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 18 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
doc/todo/separate_annex.largefiles.git-add_and_annex.largefiles.git-annex-add_settings/comment_1_affdfd11cee2c6bfe5a2ed434708ee64._comment Normal file
View file

@ -0,0 +1,18 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2019-10-22T17:23:54Z"
content="""
I am not convinced that making this configurable does anything other than
give users a new way to shoot themselves in their foot, and adding another
config setting I have to tease out of them in the ensuring bug report.
My comment on [[forum/lets_discuss_git_add_behavior]] describes scenarios
where such a git add behavior would result in accidentially adding large
files to the git object store.
The only way that would seem to avoid that is a config setting that
disables all support for populating annexed unlocked files, as well as
making git-add not smudge them, so the repository is basically treated
just like a v5 repository.
"""]]