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:44 UTC
Message-ID
<450196A1AAAE4B42A00A8B27A59278E709F07452@EXCHANGE.trad.tradestation.com>
In-Reply-To
<3e8340490903020033l78329c82la186cadaa528bc32@mail.gmail.com>

===Re:=== So, if I understand correctly, you've manually applied (manually applying diffs or something?) your changes from the release branch to the dev branch, and now want to inform git of what happened?

If so, you could commit what you have now, use a graft to change its parentage, then git-filter-branch to actually update the commit object. Something like this, I believe: git commit -m 'Merge .....' echo '<full 40-character commit ID of the merge> <parent on the dev branch> <parent on the release branch>' >> .git/info/grafts git-filter-branch dev~..dev ## You can remove (that line from) .git/info/grafts now

In the future, you may want to perform this sort of incremental merge by simply git merging intermediate revisions in the release branch. ===end===

That's very interesting. I did not find 'grafts' in the documentation, but I looked for it now that I know about it. So you can add another parent to the graph just by adding a line to that file. BTW, filter-branch isn't available on msysgit. But leaving it in that grafts file should be OK -- is that pushed/pulled with everything else?

--John
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: Bryan DonlanNext: Johannes Sixt
Message 6 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.