diff options
| author |  https://id.koumbit.net/anarcat <https://id.koumbit.net/anarcat@web> | 2015-02-11 15:01:38 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2015-02-11 15:01:38 +0000 |
| commit | f638eff8d4b04784b08e10d1cca58bb6cab0dc45 (patch) | |
| tree | d3a0a52a467b3553d3ac49c8f5f47915dd590c46 | |
| parent | 879abe6dd00bff4c7ce4866e88e7b86f86abb092 (diff) | |
| -rw-r--r-- | doc/todo/do_not_commit_with_empty_messages.mdwn | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/todo/do_not_commit_with_empty_messages.mdwn b/doc/todo/do_not_commit_with_empty_messages.mdwn new file mode 100644 index 000000000..d835bfd79 --- /dev/null +++ b/doc/todo/do_not_commit_with_empty_messages.mdwn @@ -0,0 +1,10 @@ +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]] |