diff options
Diffstat (limited to 'doc/todo/do_not_commit_with_empty_messages')
2 files changed, 0 insertions, 28 deletions
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 deleted file mode 100644 index c2cd7833f..000000000 --- a/doc/todo/do_not_commit_with_empty_messages/comment_1_3cff336e58c26eafade4a37b0c9e0634._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!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. -"""]] diff --git a/doc/todo/do_not_commit_with_empty_messages/comment_2_46a80050beba50360b1c212a9ab5a6b2._comment b/doc/todo/do_not_commit_with_empty_messages/comment_2_46a80050beba50360b1c212a9ab5a6b2._comment deleted file mode 100644 index 0ce37dc7c..000000000 --- a/doc/todo/do_not_commit_with_empty_messages/comment_2_46a80050beba50360b1c212a9ab5a6b2._comment +++ /dev/null @@ -1,17 +0,0 @@ -[[!comment format=mdwn - username="https://id.koumbit.net/anarcat" - subject="git bug indeed" - date="2015-02-11T18:14:34Z" - content=""" -i agree. this does seems like a bug in git. i tried various ways of coercing git into doing what i need, but in the end just ended up adding comments to those commits. - -i thought of reporting this to the mailing list, but it turns out there's already patches floating around to fix a bunch of issues with rebase: - -<http://search.gmane.org/?query=rebase+empty+commit+message&group=gmane.comp.version-control.git> - -in particular: - -<http://article.gmane.org/gmane.comp.version-control.git/255411/> - -not sure what those will become. -"""]] |