summaryrefslogtreecommitdiff
path: root/doc/todo/do_not_commit_with_empty_messages/comment_1_3cff336e58c26eafade4a37b0c9e0634._comment
diff options
context:
space:
mode:
Diffstat (limited to 'doc/todo/do_not_commit_with_empty_messages/comment_1_3cff336e58c26eafade4a37b0c9e0634._comment')
-rw-r--r--doc/todo/do_not_commit_with_empty_messages/comment_1_3cff336e58c26eafade4a37b0c9e0634._comment11
1 files changed, 0 insertions, 11 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.
-"""]]