response; cleanup

This commit is contained in:
Joey Hess 2019-05-03 11:37:41 -04:00
parent e7ec6f548e
commit 8c4b1d6f1f
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 14 additions and 11 deletions

View file

@ -22,18 +22,12 @@ contains the date the field was last changed. Unlike other metadata,
this cannot be directly modified by this command. It is updated this cannot be directly modified by this command. It is updated
automatically. automatically.
Note that the metadata is attached to the particular content of a file, Note that the metadata is attached to git-annex key corresponding to the
not to a particular filename on a particular git branch. More precisely, content of a file, not to a particular filename on a particular git branch.
metadata is attached to the key used for the file, which can reflect
file contents and/or name, depending on the key-value backend used for the file.
All files with the same key share the same metadata, which is All files with the same key share the same metadata, which is
stored in the git-annex branch. If a file is edited, old stored in the git-annex branch. If a file is modified, the metadata
metadata will be copied to the new key when you [[git-annex-add]] of the previous version will be copied to the new key when git-annex adds
the edited file. Note also that changes to a file's git-annex metadata will the modified file.
not be reflected in the git log of the file, since they are stored on the
git-annex branch. To attach metadata to a particular path,
rather than a particular key, use .gitattributes .
# OPTIONS # OPTIONS

View file

@ -0,0 +1,9 @@
[[!comment format=mdwn
username="joey"
subject="""comment 4"""
date="2019-05-03T15:34:07Z"
content="""
I did not write that, Ilya did. I agree that it was confusing that it was
talking about some entirely different kind of metadata, and have reworded
it.
"""]]