diff options
Diffstat (limited to 'doc/todo')
| -rw-r--r-- | doc/todo/do_not_commit_with_empty_messages.mdwn | 5 | ||||
| -rw-r--r-- | doc/todo/do_not_commit_with_empty_messages/comment_1_3cff336e58c26eafade4a37b0c9e0634._comment | 11 |
2 files changed, 16 insertions, 0 deletions
diff --git a/doc/todo/do_not_commit_with_empty_messages.mdwn b/doc/todo/do_not_commit_with_empty_messages.mdwn index d835bfd79..3c6c8415a 100644 --- a/doc/todo/do_not_commit_with_empty_messages.mdwn +++ b/doc/todo/do_not_commit_with_empty_messages.mdwn @@ -8,3 +8,8 @@ Could not commit staged changes. </pre> This was trying to fix [[a broken merge|forum/canceling_wrong_repository_merge/]]... --[[anarcat]] + +> While I think it's silly to use empty dummy commit messages when there +> is nothing of value to say about the commit, I guess I can add value +> by putting in the name of the repository where the commit was made. So, +> [[done]] --[[Joey]] diff --git a/doc/todo/do_not_commit_with_empty_messages/comment_1_3cff336e58c26eafade4a37b0c9e0634._comment b/doc/todo/do_not_commit_with_empty_messages/comment_1_3cff336e58c26eafade4a37b0c9e0634._comment new file mode 100644 index 000000000..c2cd7833f --- /dev/null +++ b/doc/todo/do_not_commit_with_empty_messages/comment_1_3cff336e58c26eafade4a37b0c9e0634._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-02-11T17:15:04Z" + content=""" +It's completely legal for git commits to have empty commit messages. Why +would rebase care? Seems like a bug in rebase. + +Note that only the git-annex assistant currently uses empty commit +messages. +"""]] |