Re: [BUG] - "git commit --amend" commits, when exiting the editor with no changes written

From: Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date: Feb 3, 2010, 18:47 UTC
Message-ID: <vpqzl3q2m2n.fsf@bauges.imag.fr>
In-Reply-To: <76c5b8581002030745g634d6ec1hb9e87b687e58e521@mail.gmail.com>

Eugene Sajine <euguess@gmail.com> writes:

> Tell me you're not serious, please;) I'm working with computers for
> more than 20 years and I do understand how editors are opening files.
> If you are serious though...:

I'm damned serious. If you've been working for 20 years with computers, you probably understand what "no change need to be saved" mean.

> The solution should be as Avery proposed - to monitor file
> modification timestamp as well as the content.

Try it. I do mean "try it". I don't think anyone will be able to explain you better than it has already been done, but ... it doesn't work.

So, again, stop arguing, try it, and see by yourself. I promise public apologies if you prove me wrong with an actually working piece of code.

> Timestamp should be remembered by git when editor is fired up and then
> checked when you're exiting the editor.

Which doesn't work reliable, as you would have noticed by reading my message.

(and yes, I'm tired and angry after a long day of work ;-) ).

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/