diff options
author | http://joey.kitenet.net/ <joey@web> | 2012-02-24 20:52:51 +0000 |
---|---|---|
committer | admin <admin@branchable.com> | 2012-02-24 20:52:51 +0000 |
commit | 0aa7f19c93e40c1cca11d7ab131c6ebb7b0a71ed (patch) | |
tree | ae54294d1052c0cc3ec53958a5be66a275ba8c31 /doc | |
parent | 21216becb4edb9ea115874f2be7cd715b8f198b2 (diff) |
Added a comment
Diffstat (limited to 'doc')
-rw-r--r-- | doc/forum/Automatic_commit_messages_for_git_annex_sync/comment_1_ea2ec57bc695da4df8a30a35d433959d._comment | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/forum/Automatic_commit_messages_for_git_annex_sync/comment_1_ea2ec57bc695da4df8a30a35d433959d._comment b/doc/forum/Automatic_commit_messages_for_git_annex_sync/comment_1_ea2ec57bc695da4df8a30a35d433959d._comment new file mode 100644 index 000000000..c07dd4999 --- /dev/null +++ b/doc/forum/Automatic_commit_messages_for_git_annex_sync/comment_1_ea2ec57bc695da4df8a30a35d433959d._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="http://joey.kitenet.net/" + nickname="joey" + subject="comment 1" + date="2012-02-24T20:52:51Z" + content=""" +Took me a minute to see this is not about [[bugs/wishlist:_more_descriptive_commit_messages_in_git-annex_branch]], but about the \"git-annex automatic sync\" message that is used when committing any changes currently on the master branch before doing the rest of the sync. + +So.. It would be pretty easy to `ls-files` the relevant files before the commit and make a message. Although this would roughly double the commit time in a large tree, since that would walk the whole tree again (git commit -a already does it once). Smarter approaches could be faster.. perhaps it could find unstaged files, stage them, generate the message, and then `git commit` the staged changes. + +But, would this really be useful? It's already easy to get `git log` to show a summary of the changes made in such a commit. So it's often seen as bad form to unnecessarily mention which files a commit changes in the commit message. + +Perhaps more useful would be to expand the current message with details like where the sync is being committed, or what +remotes it's going to sync from, or something like that. +"""]] |