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 2021-01-04 12:04:01 -04:00
parent 409eeed014
commit 89f923135d
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 17 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

17
doc/forum/Reverse_index_key_to_list_of_file_paths/comment_1_acae766349a036040a03e75fa8ed34c6._comment Normal file
View file

@ -0,0 +1,17 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2021-01-04T15:58:24Z"
content="""
> How would I make sure that potential moves/renames will update the index?
If I had a good answer to that question I would have built it already.
I mean, a post-commit hook can notice changed after the fact, but noticing
them when they've just been staged is harder.
It does not make sense to store such an index in the git-annex branch,
because it's redundant information to what's already stored in git trees.
This is discussed in [[todo/cache_key_info]].
"""]]