linux-kernel - Re: linux-next: manual merge of the kconfig tree with the kbuild 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] [day] [month] [year] [list]

Date:	Mon, 24 Aug 2009 20:33:13 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
cc:	Dick Streefland <dick@...eefland.net>, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org, Sam Ravnborg <sam@...nborg.org>
Subject: Re: linux-next: manual merge of the kconfig tree with the kbuild
 tree


On Tue, 25 Aug 2009, Stephen Rothwell wrote:

> Hi Steve,
> 
> On Mon, 24 Aug 2009 10:54:04 -0400 (EDT) Steven Rostedt <rostedt@...dmis.org> wrote:
> >
> > On Mon, 24 Aug 2009, Dick Streefland wrote:
> > 
> > > My simplified script that you merged from the kbuild tree will also
> > > extract config information from ELF files. So both patches from the
> > > kconfig tree are not needed anymore.
> > 
> > OK what is the proper way to resolve this, before sending anything off to 
> > Linus?  Should I pull in Dick's tree and resolve the conficts myself, and 
> > let you repull? Or is something else recommended?
> 
> You could cherry-pick Dick's commit into your tree (and remove your
> conflicting commits by rebasing). Or you could rebase your work on top of
> Sam's kbuild tree (or merge Sam's tree) (but that would require Sam to
> guarantee that his tree won't be rebased). Or you could do the rebase and
> then just submit your tree to Sam for inclusion (instead of, or as well
> as, it being included in linux-next directly).  Or you could keep going
> the way you are and resolve the conflict once one of the trees has been
> merged into Linus' tree.
> 
> For the moment, I can keep resolving the conflict.

Yeah, lets just keep it as is for the moment. When Sam's is accepted into 
Linus's I'll rebase off of that. Assuming that Sam's will be accepted 
rather quickly ;-)

-- Steve

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/