From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jan Kara <jack@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Stephen Tweedie <sct@redhat.com>,
linux-ext4@vger.kernel.org, Andreas Dilger <adilger@sun.com>
Subject: Re: A tree to pull into linux-next
Date: Thu, 16 Jul 2009 16:48:26 +1000 [thread overview]
Message-ID: <20090716164826.f4edbd42.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20090715193742.GA18583@duck.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]
Hi Jan,
On Wed, 15 Jul 2009 21:37:42 +0200 Jan Kara <jack@suse.cz> 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@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next parent reply other threads:[~2009-07-16 6:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090715193742.GA18583@duck.suse.cz>
2009-07-16 6:48 ` Stephen Rothwell [this message]
2009-07-16 10:45 ` A tree to pull into linux-next Jan Kara
2009-07-16 11:56 ` Stephen C. Tweedie
2009-07-16 11:47 ` Theodore Tso
2009-07-16 11:52 ` Jan Kara
2009-07-21 6:08 ` Stephen Rothwell
2009-07-21 6:15 ` Andrew Morton
2009-07-21 6:27 ` Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090716164826.f4edbd42.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=adilger@sun.com \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=sct@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox