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

Re: [PATCH] Adding rebase merge strategy

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 1, 2007, 22:28 UTC
Message-ID
<7vir5qqxl6.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<550f9510710011441t1eb50352ofc8db77f79d794d5@mail.gmail.com>
"Tom Clarke" <tom@u2i.com> writes:
Show 6 quoted lines
> I'm happy to try to address the issues you raised, but I wonder if we
> would do better to look back at my original proposal which was to add
> a --rebase option to git-pull. git-pull is the main place there I see
> need for using a rebase instead of a merge, as anywhere where you
> might use git-merge directly, if what you really want is a rebase, you
> can just run git-rebase.

Yeah, we have taught "git-pull == git-fetch + git-merge" to our users, and "-s strategy" has been a way to specify _how_ the merge is done, and not about doing something that is not a merge.

As you say, rebase is not doing a merge.  But neither is "squash".

"git-pull --rebase == git-fetch + git-rebase" might be simpler for end users to understand. I dunno.

Previous: J. Bruce Fields
Message 19 of 19 in “Adding rebase merge strategy”
  1. Adding rebase merge strategyTom Clarke, Sep 28, 2007
  2. Johannes SchindelinSep 28, 2007
  3. Tom ClarkeSep 28, 2007
  4. Adding rebase merge strategyTom Clarke, Oct 1, 2007
  5. Johannes SchindelinOct 1, 2007
  6. Junio C HamanoOct 1, 2007
  7. Tom ClarkeOct 1, 2007
  8. Carl WorthOct 1, 2007
  9. Tom ClarkeOct 1, 2007
  10. Shawn O. PearceOct 1, 2007
  11. Carl WorthOct 1, 2007
  12. Junio C HamanoOct 1, 2007
  13. Johannes SchindelinOct 2, 2007
  14. Tom ClarkeOct 2, 2007
  15. Junio C HamanoOct 2, 2007
  16. Tom ClarkeOct 3, 2007
  17. Johannes SchindelinOct 3, 2007
  18. J. Bruce FieldsOct 1, 2007
  19. Junio C HamanoOct 1, 2007

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.