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

Merge branch 'master' of ssh://git-annex.branchable.com

Browse source
This commit is contained in:
Joey Hess 2017-07-02 13:26:24 -04:00
commit 5e77f19fe9
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 12 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
doc/todo/tracking_changes_to_metadata/comment_2_03a631beaa20a479f5016def7585d363._comment Normal file
View file

@ -0,0 +1,12 @@
[[!comment format=mdwn
username="glasserc"
avatar="http://cdn.libravatar.org/avatar/8e865c04033751520601e9c15e58ddc4"
subject="comment 2"
date="2017-07-02T02:56:19Z"
content="""
I agree that a human-readable commit message is probably the wrong place to put it. I didn't know about `git annex log` but that sounds helpful. I wouldn't need it to be fast -- it would be for rare interactive use.
I'd like to not just be able to see what changed with the metadata but store a description of why as well, which is why I thought of commit messages. Would your design support that?
Thanks for your consideration.
"""]]