git-annex/doc/todo/do_not_commit_with_empty_messages.mdwn

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]]
2015-02-11 15:01:38 +00:00			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]]`
sync, assistant: Include repository name in head branch commit message. Note that while the assistant detects changes made to remote names, I left the commit message fixed rather than calculating it after every commit. It doesn't seem worth the CPU to do the latter. 2015-02-11 17:33:55 +00:00
			`> 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]]`