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

Re: [PATCH] rebase: use reflog to find common base with upstream

From
John Keeping <john@keeping.me.uk>
Date
Oct 16, 2013, 19:44 UTC
Message-ID
<20131016194444.GQ27238@serenity.lan>
In-Reply-To
<20131016192412.GK9464@google.com>
On Wed, Oct 16, 2013 at 12:24:13PM -0700, Jonathan Nieder wrote:
Show 12 quoted lines
> John Keeping wrote:
> 
> >                                    Since commit d44e712 (pull: support
> > rebased upstream + fetch + pull --rebase, 2009-07-19), pull has actually
> > chosen the most recent reflog entry which is an ancestor of the current
> > branch if it can find one.
> >
> > Change rebase so that it uses the same logic.
> 
> Nice idea.
> 
> Could pull be made to rely on rebase for this as a follow-up?

It's not an obvious change to do that (at least to me) - pull does the different steps of figuring out the base and then rebasing at different points in the script.

Show 12 quoted lines
> [...]
> > --- a/git-rebase.sh
> > +++ b/git-rebase.sh
> > @@ -437,6 +437,14 @@ then
> >  			error_on_missing_default_upstream "rebase" "rebase" \
> >  				"against" "git rebase <branch>"
> >  		fi
> > +		for reflog in $(git rev-list -g "$upstream_name" 2>/dev/null)
> > +		do
> > +			if test "$reflog" = "$(git merge-base "$reflog" HEAD)"
> 
> "git merge-base --is-ancestor" is faster.
We should probably change git-pull to use that as well.
Show 12 quoted lines
> What should happen if HEAD is not a valid commit?  (Tested with:
> 
> 	$ git checkout --orphan foo
> 	$ cat >>.git/config <<EOF
> 	[branch "foo"]
> 		remote = origin
> 		merge = refs/heads/master
> 	EOF
> 	$ bin-wrappers/git rebase 2>&1 | wc -l
> 	83
> 
> ).

Adding "2>/dev/null" to the merge-base line silences most of that, all we're left with is "fatal: Needed a single revision" which is the same as I get from master's git-rebase. I think silencing stderr is the right thing to do here - in the worst case we just use the merge-base of the two branches instead of the appropriate reflog entry.

Show 13 quoted lines
> diff --git i/git-rebase.sh w/git-rebase.sh
> index fd36cf7..d2e2c2e 100755
> --- i/git-rebase.sh
> +++ w/git-rebase.sh
> @@ -439,7 +439,7 @@ then
>  		fi
>  		for reflog in $(git rev-list -g "$upstream_name" 2>/dev/null)
>  		do
> -			if test "$reflog" = "$(git merge-base "$reflog" HEAD)"
> +			if git merge-base --is-ancestor "$reflog" HEAD
>  			then
>  				upstream_name=$reflog
>  				break
Previous: Jonathan NiederNext: Martin von Zweigbergk
Message 3 of 35 in “rebase: use reflog to find common base with upstream”
  1. rebase: use reflog to find common base with upstreamJohn Keeping, Oct 16, 2013
  2. Jonathan NiederOct 16, 2013
  3. John KeepingOct 16, 2013
  4. Martin von ZweigbergkOct 21, 2013
  5. John KeepingOct 21, 2013
  6. Martin von ZweigbergkOct 22, 2013
  7. Junio C HamanoOct 24, 2013
  8. 0/2 finding the fork point from reflog entriesJunio C Hamano, Oct 24, 2013
  9. 1/2 merge-base: use OPT_CMDMODE and clarify the command line parsingJunio C Hamano, Oct 24, 2013
  10. 2/2 merge-base: "--reflog" mode finds fork point from reflog entriesJunio C Hamano, Oct 24, 2013
  11. Eric SunshineOct 24, 2013
  12. Junio C HamanoOct 24, 2013
  13. Eric SunshineOct 24, 2013
  14. Junio C HamanoOct 24, 2013
  15. 2/2 merge-base: "--reflog" mode finds fork point from reflog entriesJunio C Hamano, Oct 24, 2013
  16. Johannes SixtOct 25, 2013
  17. John KeepingOct 25, 2013
  18. Johannes SixtOct 25, 2013
  19. Junio C HamanoOct 25, 2013
  20. 2/2 merge-base: teach "--fork-point" modeJunio C Hamano, Oct 25, 2013
  21. Eric SunshineOct 25, 2013
  22. Martin von ZweigbergkOct 26, 2013
  23. Junio C HamanoOct 28, 2013
  24. John KeepingOct 26, 2013
  25. Junio C HamanoOct 28, 2013
  26. John KeepingOct 29, 2013
  27. Junio C HamanoOct 29, 2013
  28. John KeepingOct 24, 2013
  29. Junio C HamanoOct 24, 2013
  30. John KeepingOct 24, 2013
  31. John KeepingOct 24, 2013
  32. John KeepingOct 24, 2013
  33. Junio C HamanoOct 25, 2013
  34. Martin von ZweigbergkOct 22, 2013
  35. John KeepingOct 24, 2013

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.