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

Re: [Q] merging from one (kernel) stable to another?

From
BFBrian Foster <brian.foster@innova-card.com>
Date
Mar 30, 2009, 11:58 UTC
Message-ID
<200903301358.48864.brian.foster@innova-card.com>
In-Reply-To
<49D0A133.80503@viscovery.net>
On Monday 30 March 2009 12:38:43 Johannes Sixt wrote:
> Andreas Ericsson schrieb:
> > A possibly better approach for you is to "git format-patch"
> > your own changes and apply them to a clean 2.6.26.8 tree
> > instead of trying to merge 2.6.26.8 into 2.6.21.
[ I'm going from .21 to .26.8, so I think you've got that reversed? ]
Show 7 quoted lines
> 
> After you have successfully done *that*, you know how the resulting
> tree must look like, and you give it a tag, say "like-this".
> If you really want to have a merge, then you can just repeat the
> merge with your original branch, at which time you will get tons
> of conflicts.  Now you just 'git checkout like-this -- .' and you
> have all your conflicts resolved in the way you need them.
Andreas & Hannes,
  Thanks for the suggestion.  I'll have to experiment,
 but off-the-top-of-my-head, I think I do want a merge,
 so that it's easier to track the history of individual
 local changes.  Having said that, I'm not entirely sure
 I follow your suggestions.  What I think you mean is:
  (1)  Create a patch which is all (local) changes
         (née diffs) from linux-mips.21 to our.21;
  (2)  Checkout linux-mips.26.8 (e.g.);
  (3)  Apply the patch created in (1), above;
  (4)  Tag the result `like-this';
  (5)  Checkout our.21;  and
  (6)  Merge with `like-this'.
 I admit that now that I write the steps out, it seems
 to make sense ....?   Am I understanding correctly?
  Thanks for the suggestions.  Other suggestions are also
 quite welcome.
cheers!
	-blf-
-- 
“How many surrealists does it take to   | Brian Foster
 change a lightbulb? Three. One calms   | somewhere in south of France
 the warthog, and two fill the bathtub  |   Stop E$$o (ExxonMobil)!
 with brightly-coloured machine tools.” |      http://www.stopesso.com
Previous: Johannes SixtNext: Johannes Sixt
Message 4 of 14 in “[Q] merging from one (kernel) stable to another?”
  1. Brian FosterMar 30, 2009
  2. Andreas EricssonMar 30, 2009
  3. Johannes SixtMar 30, 2009
  4. Brian FosterMar 30, 2009
  5. Johannes SixtMar 30, 2009
  6. Brian FosterMar 30, 2009
  7. Andreas EricssonMar 30, 2009
  8. Brian FosterMar 30, 2009
  9. Andreas EricssonMar 30, 2009
  10. Ping YinMar 30, 2009
  11. Kris ShannonMar 31, 2009
  12. Daniel BarkalowMar 30, 2009
  13. Brian FosterMar 31, 2009
  14. Uwe Kleine-KönigMar 30, 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.