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

RE: proper way to merge?

From
JDJohn Dlugosz <jdlugosz@tradestation.com>
Date
Mar 2, 2009, 22:19 UTC
Message-ID
<450196A1AAAE4B42A00A8B27A59278E709F07432@EXCHANGE.trad.tradestation.com>
In-Reply-To
<43d8ce650902272358h4219f439qfa60ba7a7e0d222f@mail.gmail.com>

===Re:=== Instead of merge, I prefer to rebase. so:

git checkout dev git rebase origin rel

This replays each commit made in 'dev' on top of release, letting you fix each commit separately. It also means that when I commit to release, the changes are a nice tree. ===end===

The reason I'm doing this -- why I took over maintenance of the repository -- is because I strenuously objected to his plan to "rebase".  NO!  Merge, don't rebase.  Besides never rebasing published branches, in this case it works much better the other way around:  dev made systemic changes, and rel is mostly patches and completely new pieces of code.  After looking at what was in dev..rel and what was in rel..dev, I chose to start with dev and bring in the commits from rel in a controlled manner.
I think you are indicated that the rebase is easier because the merge is done one commit at a time rather than in one huge bang.  I want to have that advantage and then some by picking related groups of commits and verifying that it still compiles before getting more, not even limited to the original order.
I'll post what I learned in a separate note.

--John (excuse the footer; it's not my choice)

TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and subscription company, and TradeStation Europe Limited, a United Kingdom, FSA-authorized introducing brokerage firm. None of these companies provides trading or investment advice, recommendations or endorsements of any kind. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
Previous: John TapsellNext: John Tapsell
Message 3 of 9 in “proper way to merge?”
  1. John DlugoszFeb 27, 2009
  2. John TapsellFeb 28, 2009
  3. John DlugoszMar 2, 2009
  4. John TapsellMar 3, 2009
  5. Bryan DonlanMar 2, 2009
  6. John DlugoszMar 2, 2009
  7. Johannes SixtMar 3, 2009
  8. John DlugoszMar 3, 2009
  9. Johannes SixtMar 3, 2009

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.