Thien-Thi Nguyen <ttn@xxxxxxxxxxx> writes: > () Junio C Hamano <gitster@xxxxxxxxx> > () Fri, 28 Dec 2007 14:01:55 -0800 > > Was it a buggy "git commit" command, or a bad commit log > message was fed to "git commit" by the user, and there is > nothing for me to worry about? > > i'm sorry, even though it was only a couple days ago, the actual > events are far back in my memory, so i can't say. i wouldn't > worry about it -- probably user error. (i'm new w/ git. most of > the time i drive it from w/in emacs, which is well behaved; it is > when i leave that comparative safety to do some flailing from the > command-line that things go weird.) > > i suppose one way to improve git would be to test how it handles > interruption (control-c in the middle of a commit, for example). > a bit tricky to arrange (reproducibly), though... > > now i go search the docs for how to replace that log message. "git-rebase -i" - 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
