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 2022-09-15 12:39:07 -04:00
parent 7a4006cc07
commit 6f31bd4755
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 24 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

24
doc/forum/Unlocked_mode_without_data_also_under_.git__47__annex__63__/comment_5_97fd65626991b1e8012e15595941d25d._comment Normal file
View file

@ -0,0 +1,24 @@
[[!comment format=mdwn
username="joey"
subject="""comment 5"""
date="2022-09-15T16:27:54Z"
content="""
Ah, oops.. I was thinking about BTRFS..
However, getting back to the original motivation of jgoerzen to
request this, it seems to come down to making a hard link being seen as
"mucking with the source data". That seems like a very weak reason to make
such a very large change to git-annex, that would only be safe in a
small and poorly defined set of circumstances.
And it would be a large change, because currently git-annex can broadly
assume that any time a .git/annex/objects/ file exists, the content
is present in the repository. Every place that makes that assumption
would need to instead check if any of the known work tree files that use
the object are populated with the content (or at least are not annex
pointer files).
(jgoerzen also mentions timestamps, but git-annex preserves those
when ingesting files. Of course timestamp data is not recorded in the git
repository unless you use some other tool to do so.)
"""]]