linux-kernel - Re: [PATCH 2.6.26-rc5 0/2] cris: compile fixes for 2.6.26-rc5

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]

Date:	Tue, 10 Jun 2008 20:15:01 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Jesper Nilsson <Jesper.Nilsson@...s.com>
Cc:	Adrian Bunk <bunk@...nel.org>,
	"Hinko Ko??evar" <hinko.kocevar@...rtapot.si>,
	Mikael Starvik <mikael.starvik@...s.com>,
	<linux-kernel@...r.kernel.org>, dev-etrax <dev-etrax@...s.com>
Subject: Re: [PATCH 2.6.26-rc5 0/2] cris: compile fixes for 2.6.26-rc5

Hi Jasper,

On Tue, 10 Jun 2008 11:49:37 +0200 Jesper Nilsson <Jesper.Nilsson@...s.com> wrote:
>
> Have I understood correctly that a tree exported for -next can be rebased
> without causing any problems? I've hesitated a bit to create a -next tree
> to avoid problems with later merges.

Yes, rebases are OK (but not encouraged :-)).  The rules are that stuff in
the tree for -next must have been posted somewhere appropriate, reviewed,
and unit tested as much as possible and be reasonably expected to be in
the next merge window.

I also merge trees containing fixes for Linus' current tree.

Also, I accept git trees or quilt series.
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped