linux-kernel - Re: Pull request for nilfs2 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]

Message-Id: <20090414075559.53b648ee.sfr@canb.auug.org.au>
Date:	Tue, 14 Apr 2009 07:55:59 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Ryusuke Konishi <konishi.ryusuke@....ntt.co.jp>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Pull request for nilfs2 tree

Hi,

On Mon, 13 Apr 2009 17:29:31 +0900 (JST) Ryusuke Konishi <konishi.ryusuke@....ntt.co.jp> wrote:
>
> Could you consider pulling the for-next branch of this tree:
> 
>    git://git.kernel.org/pub/scm/linux/kernel/git/ryusuke/nilfs2.git
> 
> into linux-next, please?

It will be in linux-next starting today.

What I tell everyone: all patches/commits in the tree/series must
have been:

	posted to a relevant mailing list
	reviewed
	unit tested
	destined for the next merge window (or the current release)

*before* they are included.  The linux-next tree is for integration
testing and to lower the impact of conflicts between subsystems in the
next merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped