From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Borislav Petkov <petkovbb@googlemail•com>
Cc: Borislav Petkov <borislav.petkov@amd•com>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Ingo Molnar <mingo@elte•hu>
Subject: Rebasing the edac-amd tree (Was: Re: linux-next: manual merge of the edac-amd tree with Linus' tree)
Date: Wed, 5 Aug 2009 16:40:32 +1000 [thread overview]
Message-ID: <20090805164032.3cf9d95a.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20090805062215.GA7732@liondog.tnic>
[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]
Hi Boris,
On Wed, 5 Aug 2009 08:22:15 +0200 Borislav Petkov <petkovbb@googlemail•com> wrote:
>
> thanks and yes, you're right. The former patch is less intrusive
> and we opted for that one since it is really late in the -rc cycle
> but the latter cleans up stuff so that code flow becomes much more
> understandable. I'll rediff later and sorry for the inconvenience.
As an alternative to rebasing, you could merge Linus' current tree into
yours and do the merge fixup there. This is not particularly necessary,
as the fixup is fairly simple. Though you may want to do that sometime
before you ask Linus to merge your tree.
> By the way, I see that you're merging edac-amd before tip and I'm going
> to need to rebase my tree against tip in the next couple of days since
> it depends on a bunch of stuff in it, so could you please switch the
> merge order of the two trees so that edac-amd goes after tip?
Again, instead of rebasing, you could just merge in the branches from tip
that you depend on. You need to make sure that you only depend on stable
(i.e. non rebasing) branches in the tip tree, not on the branch
(auto-latest) that is actually merged into linux-next. Please discuss
this with Ingo.
I will move the edac-amd tree to after the tip tree tomorrow.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-08-05 6:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 5:09 linux-next: manual merge of the edac-amd tree with Linus' tree Stephen Rothwell
2009-08-05 6:22 ` Borislav Petkov
2009-08-05 6:40 ` Stephen Rothwell [this message]
2009-08-05 7:42 ` Rebasing the edac-amd tree (Was: Re: linux-next: manual merge of the edac-amd tree with Linus' tree) Borislav Petkov
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=20090805164032.3cf9d95a.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=borislav.petkov@amd$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=petkovbb@googlemail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox