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

Why the default action for pull is merge, but not rebase?

From
ESEugene Sajine <euguess@gmail.com>
Date
Oct 27, 2010, 16:46 UTC
Message-ID
<AANLkTinLbaE6He-bxA_+CT6J5uWmZSgodGs6SXO7eqnr@mail.gmail.com>
Hi,

I'm just curious if there are some downsides that i don't see? For me it seems to have much more sense to automatically rebase vs merge when you do pull. The diverged history will become "straighter" and cleaner, if the history is not diverged then it will be fast-forward. So, why not to rebase?

Thanks for your time in advance,
Eugene
Next: Jonathan Nieder
Message 1 of 13 in “Why the default action for pull is merge, but not rebase?”
  1. Eugene SajineOct 27, 2010
  2. Jonathan NiederOct 27, 2010
  3. Eugene SajineOct 27, 2010
  4. Jonathan NiederOct 27, 2010
  5. Björn SteinbrinkOct 28, 2010
  6. Eugene SajineOct 27, 2010
  7. Jonathan NiederOct 27, 2010
  8. Eric RaibleOct 27, 2010
  9. Joshua JensenOct 28, 2010
  10. Kevin BallardOct 28, 2010
  11. Eric RaibleOct 28, 2010
  12. Kevin BallardOct 28, 2010
  13. Stefan HallerOct 28, 2010

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.