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

Re: Should "pull --rebase" try to be a little cleverer?

From
Nicolas Pitre <nico@cam.org>
Date
Jan 21, 2008, 16:42 UTC
Message-ID
<alpine.LFD.1.00.0801211140170.20753@xanadu.home>
In-Reply-To
<alpine.LSU.1.00.0801211619530.5731@racer.site>
On Mon, 21 Jan 2008, Johannes Schindelin wrote:
Show 34 quoted lines
> Hi,
> 
> On Mon, 21 Jan 2008, Nicolas Pitre wrote:
> 
> > On Mon, 21 Jan 2008, Johannes Schindelin wrote:
> > 
> > > last night an idea hit me: if I "git pull --rebase blabla master", it 
> > > could be that "blabla" decided to rebase "master" already, and ATM 
> > > this would lead to quite a few conflicts, since commits that were not 
> > > mine were rewritten.
> > 
> > Indeed.
> > 
> > > However, if we already have refs/remotes/blabla/master, we could DWIM 
> > > the --rebase call to
> > > 
> > > 	git rebase --onto FETCH_HEAD refs/remotes/blabla/master
> > 
> > I was believing this was already the case.  Mind you, I never verified 
> > it.
> > 
> > I think the best is really to have the equivalent of:
> > 
> > 	git fetch blabla/master
> > 	git rebase --onto blabla/master blabla/master@{1} HEAD
> 
> Not exactly... what would you do with this:
> 
> 	git pull --rebase git://git.kernel.org/... master
> 
> Hm?
> 
> So I think that _only_ in the case that a remote ref is updated, _and_ 
> that there is already one, can we do the DWIMery.
Well, sure.  That's the case I care about.
Nicolas
Previous: Johannes SchindelinNext: Junio C Hamano
Message 4 of 8 in “Should "pull --rebase" try to be a little cleverer?”
  1. Johannes SchindelinJan 21, 2008
  2. Nicolas PitreJan 21, 2008
  3. Johannes SchindelinJan 21, 2008
  4. Nicolas PitreJan 21, 2008
  5. Junio C HamanoJan 21, 2008
  6. pull --rebase: be cleverer with rebased upstream branchesJohannes Schindelin, Jan 26, 2008
  7. Junio C HamanoJan 26, 2008
  8. Johannes SchindelinJan 26, 2008

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.