Jeff King schrieb: > It _is_ generally hard to get an empty commit message using "git > commit". But it's possible there is a bug in cherry-pick, rebase, or > some ohter low-level tool that accidentally erased your message > as the commit was moved. Since this is on Windows, chances are that this is an encoding issue. If you have non-ASCII in the commit message, but i18n.commitEncoding is unset, then you can introduce invalid UTF8 sequences easily. This could confuse one of the pipelines (rebase, am, cherry-pick, etc). You should set git config i18n.commitencoding cp1252 (or whatever is appropriate for you locale). I even have git config i18n.logoutputencoding cp850 so that I see correct umlauts if I happen to run git log without a pager in CMD ;) (I rarely do that, though.) -- Hannes -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
