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

comment, open related todo

Browse source
This commit is contained in:
Joey Hess 2019-07-19 13:10:17 -04:00
parent a7ddf2ac3a
commit cf6152575a
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 26 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
doc/forum/Unlocked_files_confusion/comment_1_6442aa304b4d44bfc6bc038f4b55f37a._comment Normal file
View file

@ -0,0 +1,15 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2019-07-19T17:02:59Z"
content="""
Your .gitattributes setting configured git-annex to not
treat metadata.db as a large file, so its content gets added to git.
git-annex does not hard link locked files by ddefault, setting annex.thin
can make it do so.
There is not currently a way to configure whether a file
is added locked or unlocked by filename. I have opened a todo
about it, [[todo/annex.addunlocked_in_gitattributes]].
"""]]

11
doc/todo/annex.addunlocked_in_gitattributes.mdwn Normal file
View file

@ -0,0 +1,11 @@
Make annex.addunlocked be able to be configured in .gitattributes,
the same way as annex.largefiles can be.
This would be useful if certain filename extensions need to be unlocked to
be used, and others are desired to be kept locked.
The annex.addunlocked git config is a boolean, but this gitattributes one
would effectively build up a file match expression. So it might then follow
that the git config should also be a file match expression, with "true"
being the same as "anything" and "false" the same as "nothing" for
back-compat. --[[Joey]]