linux-kernel - Rebasing the edac-amd tree (Was: Re: linux-next: manual merge of the edac-amd tree with Linus' tree)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20090805164032.3cf9d95a.sfr@canb.auug.org.au>
Date:	Wed, 5 Aug 2009 16:40:32 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Borislav Petkov <petkovbb@...glemail.com>
Cc:	Borislav Petkov <borislav.petkov@....com>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Ingo Molnar <mingo@...e.hu>
Subject: Rebasing the edac-amd tree (Was: Re: linux-next: manual merge of
 the edac-amd tree with Linus' tree)

Hi Boris,

On Wed, 5 Aug 2009 08:22:15 +0200 Borislav Petkov <petkovbb@...glemail.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@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped