All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Drake <dsd@gentoo.org>
To: Steve French <smfrench@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: -mm breaks and merging maintainer git trees with mainline
Date: Wed, 18 Jul 2007 19:13:28 -0400	[thread overview]
Message-ID: <469E9E98.4000003@gentoo.org> (raw)
In-Reply-To: <524f69650707181309w42d665c9ua49179b9d7e0a6b1@mail.gmail.com>

Steve French wrote:
> What is the currently recommended procedure for merging a maintainer
> tree with mainline in order to reorder all of the fixes in the
> maintainer tree, after the changes in the linux-2.6. tree (to make the
> eventual merge from Linus easier)?
> 
> In this particular case, the
> http://git.kernel.org/?p=linux/kernel/git/sfrench/cifs-2.6.git tree
> has a few dozen changesets that are not in its parent yet (and the
> cifs-2.6.git is at 2.6.22-rc5 level)
> (http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git) but
> mainline now has fixes which affect the same directory as the
> maintainer tree maintains.

I think you can do:

git checkout origin
git pull
git checkout master
git rebase origin

In general, people seem to keep "from-linus" branches which they never 
modify. I guess they only ever pull linus into there, and then rebase 
their customised branch-of-choice (master, in your case) on top of that 
one in order to keep up-to-date.

Daniel

      reply	other threads:[~2007-07-18 23:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-18 20:09 -mm breaks and merging maintainer git trees with mainline Steve French
2007-07-18 23:13 ` Daniel Drake [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=469E9E98.4000003@gentoo.org \
    --to=dsd@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smfrench@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.