Hi Jan, On Wed, 15 Jul 2009 21:37:42 +0200 Jan Kara <jack@xxxxxxx> wrote: > > I've decided to create a tree through which I can occasionally merge > mainly ext3/JBD fixes (and possibly also fixes to filesystems which > don't have a maintainer). Hopefully this reduces chances that some patches > get lost on the way... Could you please start pulling the tree below to > linux-next? Thanks. > > git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs-2.6.git for_next I am happy to include this, but (no offense) I would like to hear from the ext3 and jbd maintainers (cc'd) about it. For reference: 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@xxxxxxxxxxxxxxxx http://www.canb.auug.org.au/~sfr/
Attachment:
pgpU46z0vdaUX.pgp
Description: PGP signature
