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

Re: git-merge-subordinate

From
Shawn Pearce <spearce@spearce.org>
Date
Oct 25, 2006, 16:27 UTC
Message-ID
<20061025162758.GC9312@spearce.org>
In-Reply-To
<Pine.LNX.4.63.0610251819080.3286@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
Show 18 quoted lines
> Hi,
> 
> On Wed, 25 Oct 2006, Jakub Narebski wrote:
> 
> > Matthew Wilcox wrote:
> > 
> > > Linus doesn't like seeing unnecessary merges in his tree.  I'm not a huge
> > > fan of them either.  Wouldn't it be nice if we had a merge method that
> > > did a merge without creating a merge?  I call it git-merge-subordinate
> > > (since my tree is subordinate to the tree I'm pulling from).  I suppose
> > > you could call it 'slave' if you want to be more pithy.  Anyway, this
> > > is a first attempt, and it's totally cargo-cult programming; I make no
> > > claim that I understand what I'm doing.  But it does seem to work.
> > 
> > Hmmm... the --squash option to git-merge/git-pull isn't enough?
> 
> What subordinate does is not _merge_, but _rebase_ on top of the fetched 
> commit. So yes, --squash isn't enough ;-)

And I would suggest calling it 'git-merge-rebase', as the strategy really is rebase... :-)

Previous: Johannes Schindelin
Message 4 of 4 in “git-merge-subordinate”
  1. Matthew WilcoxOct 25, 2006
  2. Jakub NarebskiOct 25, 2006
  3. Johannes SchindelinOct 25, 2006
  4. Shawn PearceOct 25, 2006

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.