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

Re: [RFC] should `git rebase --keep-base` imply `--reapply-cherry-picks` ?

From
Denton Liu <liu.denton@gmail.com>
Date
Jul 15, 2020, 03:32 UTC
Message-ID
<20200715033216.GA11770@generichostname>
In-Reply-To
<20200714035104.1465772-1-jonathantanmy@google.com>
On Mon, Jul 13, 2020 at 08:51:04PM -0700, Jonathan Tan wrote:
Show 13 quoted lines
> > > How would a change that made '--reapply-cherry-picks' be the default when using 'keep-base'
> > > be received ?
> > 
> > I'm somewhat surprised that --no-reapply-cherry-picks is the default. I
> > would argue that it _shouldn't_ be the default at all. It's an
> > optimisation for when no --onto or --keep-base are specified but it
> > definitely can cause problems otherwise, as we've seen.
> 
> When I encountered this feature, it was a surprise to me too, but this
> has been documented as a feature for a long time (e.g. see the man page
> for 2.1.4 from 2014 [2] - search for "RECOVERING FROM UPSTREAM REBASE").
> 
> [2] https://git-scm.com/docs/git-rebase/2.1.4
Ah, I was mistaken. Thanks for the correction.
Previous: Jonathan TanNext: Phillip Wood
Message 4 of 8 in “[RFC] should `git rebase --keep-base` imply `--reapply-cherry-picks` ?”
  1. Philippe BlainJul 14, 2020
  2. Denton LiuJul 14, 2020
  3. Jonathan TanJul 14, 2020
  4. Denton LiuJul 15, 2020
  5. Phillip WoodJul 14, 2020
  6. Johannes SchindelinJul 14, 2020
  7. Denton LiuJul 15, 2020
  8. Phillip WoodJul 15, 2020

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.