blob: 3c6c8415abc608b3d2861ece7c2376d9230a6202 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
it seems that `git-annex` sometimes does commits with empty commit messages. this makes rebasing git-annex branches much much harder than they need to, because rebase freaks out on those weird commits:
<pre>
anarcat@marcos:video$ git rebase --continue
Waiting for Emacs...
Aborting commit due to empty commit message.
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]]
|
