Re: A tree to pull into linux-next

Re: A tree to pull into linux-next

[Stephen Rothwell]

[-- 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 --]

Re: A tree to pull into linux-next

[Jan Kara]

On Thu 16-07-09 16:48:26, Stephen Rothwell wrote:
> 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.
  Sure. BTW: Stephen Tweedie isn't doing ext3/jbd anymore for a few years
(probably we should remove him from MAINTAINERS)...

									Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

Re: A tree to pull into linux-next

[Stephen C. Tweedie]

Hi,

On Thu, 2009-07-16 at 12:45 +0200, Jan Kara wrote:

> > I am happy to include this, but (no offense) I would like to hear from
> > the ext3 and jbd maintainers (cc'd) about it.
>   Sure. BTW: Stephen Tweedie isn't doing ext3/jbd anymore for a few years
> (probably we should remove him from MAINTAINERS)...

ACK, sadly I'm unlikely to find time for this in the near future.

--Stephen

Re: A tree to pull into linux-next

[Theodore Tso]

On Thu, Jul 16, 2009 at 04:48:26PM +1000, Stephen Rothwell wrote:
> 
> I am happy to include this, but (no offense) I would like to hear from
> the ext3 and jbd maintainers (cc'd) about it.
> 

The main isssue would be that akpm often has ext3 changes stashed in
-mm.  Having a separate ext3 tree makes sense, and if Jan wants to
maintain it, that makes good sense to me, but we should get Andrew's
sign off, and Jan should make sure he has any ext3/jbd patches that
might be in -mm, to avoid any potential patch conflicts.

      	    	    	      - Ted

Re: A tree to pull into linux-next

[Jan Kara]

> On Thu, Jul 16, 2009 at 04:48:26PM +1000, Stephen Rothwell wrote:
> > 
> > I am happy to include this, but (no offense) I would like to hear from
> > the ext3 and jbd maintainers (cc'd) about it.
> > 
> 
> The main isssue would be that akpm often has ext3 changes stashed in
> -mm.  Having a separate ext3 tree makes sense, and if Jan wants to
> maintain it, that makes good sense to me, but we should get Andrew's
> sign off, and Jan should make sure he has any ext3/jbd patches that
> might be in -mm, to avoid any potential patch conflicts.
  Yeah. It's upto Andrew. I think he pulls linux-next so he should notice
conflicts. Anyway, I don't mind pushing the changes through him if he
likes it more that way but I've felt that he's rather busy and this
hopefully helps him a bit...

								Honza
-- 
Jan Kara <jack@suse.cz>
SuSE CR Labs

Re: A tree to pull into linux-next

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1040 bytes --]

Hi Andrew,

On Thu, 16 Jul 2009 13:52:21 +0200 Jan Kara <jack@suse.cz> wrote:
>
> > On Thu, Jul 16, 2009 at 04:48:26PM +1000, Stephen Rothwell wrote:
> > > 
> > > I am happy to include this, but (no offense) I would like to hear from
> > > the ext3 and jbd maintainers (cc'd) about it.
> > > 
> > 
> > The main isssue would be that akpm often has ext3 changes stashed in
> > -mm.  Having a separate ext3 tree makes sense, and if Jan wants to
> > maintain it, that makes good sense to me, but we should get Andrew's
> > sign off, and Jan should make sure he has any ext3/jbd patches that
> > might be in -mm, to avoid any potential patch conflicts.
>   Yeah. It's upto Andrew. I think he pulls linux-next so he should notice
> conflicts. Anyway, I don't mind pushing the changes through him if he
> likes it more that way but I've felt that he's rather busy and this
> hopefully helps him a bit...

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

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: A tree to pull into linux-next

[Andrew Morton]

On Tue, 21 Jul 2009 16:08:52 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi Andrew,
> 
> On Thu, 16 Jul 2009 13:52:21 +0200 Jan Kara <jack@suse.cz> wrote:
> >
> > > On Thu, Jul 16, 2009 at 04:48:26PM +1000, Stephen Rothwell wrote:
> > > > 
> > > > I am happy to include this, but (no offense) I would like to hear from
> > > > the ext3 and jbd maintainers (cc'd) about it.
> > > > 
> > > 
> > > The main isssue would be that akpm often has ext3 changes stashed in
> > > -mm.  Having a separate ext3 tree makes sense, and if Jan wants to
> > > maintain it, that makes good sense to me, but we should get Andrew's
> > > sign off, and Jan should make sure he has any ext3/jbd patches that
> > > might be in -mm, to avoid any potential patch conflicts.
> >   Yeah. It's upto Andrew. I think he pulls linux-next so he should notice
> > conflicts. Anyway, I don't mind pushing the changes through him if he
> > likes it more that way but I've felt that he's rather busy and this
> > hopefully helps him a bit...
> 
> Any comments?

Sure, I'm OK with sending ext3/jbd stuff in Jan's direction.

Just don't break it ;)

Re: A tree to pull into linux-next

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 355 bytes --]

Hi Jan,

On Mon, 20 Jul 2009 23:15:35 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> Sure, I'm OK with sending ext3/jbd stuff in Jan's direction.

I will add you tree to linux-next tomorrow.

> Just don't break it ;)

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

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]