From: Sverre Rabbelier Date: Tue, 27 Jan 2009 22:37:45 GMT Subject: Re: git-am annoyance Message-ID: In-Reply-To: <7vr62o1iww.fsf@gitster.siamese.dyndns.org> On Tue, Jan 27, 2009 at 23:30, Junio C Hamano wrote: > It wants to read from the stdin as "git am < mbox" is a valid usage. Ah, ofcourse, that makes sense :). > A patch to detect that the input was killed with ^C and clean things up > would be welcome. Also we may be able to detect "-t 0", too. What is '-t 0'? How would one detect this in bash? >> $ # ok, now what do I do? > > Here is one thing you could do. > > $ PS1=': $(__git_ps1 "%s"); ' > : master|AM/REBASE; > : master|AM/REBASE; git am --abort Ugh, I couldn't even get that thing to work :P. > But you are right. We should be able to detect this. That would be nice indeed. > I think it was just people who often use "am" are so used to correctly the > command that the state where no state files are created didn't happen > often and never reported the breakage. Ok, am glad I reported it then, now it's a known issue at least. -- Cheers, Sverre Rabbelier