aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar https://id.koumbit.net/anarcat <https://id.koumbit.net/anarcat@web>2015-02-11 18:14:34 +0000
committerGravatar admin <admin@branchable.com>2015-02-11 18:14:34 +0000
commited7edaaad4cbd959214e7560599c1342b4aa38a4 (patch)
treeba0fd249921783c56eabac72a140989786c7b000
parentffe56b57229cc04bae1b911d37f3d8c99da749c5 (diff)
Added a comment: git bug indeed
-rw-r--r--doc/todo/do_not_commit_with_empty_messages/comment_2_46a80050beba50360b1c212a9ab5a6b2._comment17
1 files changed, 17 insertions, 0 deletions
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
new file mode 100644
index 000000000..0ce37dc7c
--- /dev/null
+++ b/doc/todo/do_not_commit_with_empty_messages/comment_2_46a80050beba50360b1c212a9ab5a6b2._comment
@@ -0,0 +1,17 @@
+[[!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.
+"""]]