Re: Dangerous "git am --abort" behavior
- From
Drew Northup <drew.northup@maine.edu>
- Date
- Dec 20, 2010, 21:52 UTC
- Message-ID
- <1292881979.23145.5.camel@drew-northup.unet.maine.edu>
- In-Reply-To
- <loom.20101220T203122-271@post.gmane.org>
On Mon, 2010-12-20 at 19:35 +0000, Adam Monsen wrote:
Show 9 quoted lines
> Linus Torvalds writes: > > What happened today was that I had been doing a pull or two, and then > > applied an emailed patch with "git am" as usual. But as sometimes > > happens, I actually had a previous "git am" that had failed - in fact, > > it was the same patch that I applied today that had had an earlier > > version that no longer applied. > > It would be helpful if "git status" mentioned if a rebase or am operation is in > progress... this might have helped you avoid the situation described.
Adam, Please don't cull the CC list...
In any case, are there any other mult-part operations for which we might want to report "In Progress" in the "git status" output? How do we best harvest and present this information to the user? This sounds like a more general-purpose project than Linus' original scope.
-- -Drew Northup N1XIM AKA RvnPhnx on OPN ________________________________________________ "As opposed to vegetable or mineral error?" -John Pescatore, SANS NewsBites Vol. 12 Num. 59