summaryrefslogtreecommitdiff
path: root/doc/todo/do_not_commit_with_empty_messages/comment_2_46a80050beba50360b1c212a9ab5a6b2._comment
blob: 0ce37dc7cd564e4d0acacb60db435427fdfc9ff3 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
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.
"""]]