On Wed, Feb 3, 2010 at 12:48 AM, Eugene Sajine <euguess@xxxxxxxxx> wrote: >> >> This is where you're wrong. The reason why commit (without --amend) is >> aborting when you don't save is that the default commit message is >> empty, not that it wasn't saved. In fact, just saving still makes in >> abort. You need to add something to the commit message and then save >> to get it to perform the commit. >> >>> Same should be applied to rebase -i and of course to commit --amend as >>> it is still commit operation. >>> >> >> "rebase -i" and "commit --amend" already has the exact same logic as >> commit without ammend in this regard - they abort if the buffer is >> empty. >> >> -- >> Erik "kusma" Faye-Lund >> > > Thank you, but I'm not wrong, as i described the exact same thing > somewhere in my second or third message, without even knowing the > implementation details. I understand the reason WHY it is like it is, > i just don't like it as it is inconsistent and IMHO incorrect. > But you are. The interface isn't inconsistent. Your model of how it works however, is wrong. -- Erik "kusma" Faye-Lund -- 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