git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git rebase --continue automatic --skip?

From
PBPeter Baumann <waste.manager@gmx.de>
Date
Apr 11, 2011, 06:10 UTC
Message-ID
<20110411061052.GD30820@m62s10.vlinux.de>
In-Reply-To
<20110409130309.GC30820@m62s10.vlinux.de>
On Sat, Apr 09, 2011 at 03:03:09PM +0200, Peter Baumann wrote:
Show 9 quoted lines
> On Fri, Apr 08, 2011 at 08:03:51PM -0400, Jeff King wrote:
> > On Fri, Apr 08, 2011 at 01:30:01PM -0700, skillzero@gmail.com wrote:
> > 
> > > Is there a way to make git rebase --continue automatically do a --skip
> > > if a conflict resolution ends up not needing the patch? Normally, git
> > > rebase will just silently skip a patch if it's not needed, but if a
> > > patch results in a conflict and I use git mergetool and end up
> > > deleting all the changes, git rebase --continue stops and makes me
> > > explicitly use --skip.
[ ... patch left out ... ]
Show 13 quoted lines
> > 
> > I put it in rebase and not straight into "git am", as I'm not sure that
> > "am" would want to share the same behavior. I'm not sure why we haven't
> > done this up until now. Maybe there is some corner case I'm not thinking
> > of where the user would want to do something besides skip when we hit
> > this situation. I dunno.
> > 
> 
> This was mentioned before on the list (sorry, don't have a reference, 
> but it was a long time ago). AFAIR the reason it wasn't implemented yet is that
> you will lose the commit message, which might contain precious information.
> But with reflogs this shouldn't be a problem anymore.
> 
I actually managed to find the thread I was remembering:
http://thread.gmane.org/gmane.comp.version-control.git/62854/focus=62907
-Peter
Previous: Junio C HamanoNext: Junio C Hamano
Message 5 of 7 in “git rebase --continue automatic --skip?”
  1. skillzero@gmail.comApr 8, 2011
  2. Jeff KingApr 9, 2011
  3. Peter BaumannApr 9, 2011
  4. Junio C HamanoApr 10, 2011
  5. Peter BaumannApr 11, 2011
  6. Junio C HamanoApr 10, 2011
  7. Joshua JuranApr 13, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.