Re: Upstream tree for OMFS?

Re: Upstream tree for OMFS?

[Andrew Morton]

On Mon, 12 Jul 2010 11:49:01 -0400 Bob Copeland <me@bobcopeland.com> wrote:

> Hello fs devs,
> 
> I have a few patches to send on to -next for OMFS
> and I finally got around to setting up a git tree for
> it.  Previously I sent things through akpm or the
> trivial tree.
> 
> I doubt anyone but me cares too much about this FS
> but I thought I'd ask first if anyone wants to be the
> upstream instead of me sending pull requests directly
> to Linus.  Of course I'll post patches here for
> review in either case.

Please ask Stephen to include the tree in the linux-next lineup.

Re: Upstream tree for OMFS?

[Bob Copeland]

On Mon, Jul 12, 2010 at 10:44:35AM -0700, Andrew Morton wrote:
> > I doubt anyone but me cares too much about this FS
> > but I thought I'd ask first if anyone wants to be the
> > upstream instead of me sending pull requests directly
> > to Linus.  Of course I'll post patches here for
> > review in either case.
> 
> Please ask Stephen to include the tree in the linux-next lineup.

Ok - Stephen would you mind including this tree for omfs?

git://git.kernel.org/pub/scm/linux/kernel/git/bcopeland/omfs.git#for-next

-- 
Bob Copeland %% www.bobcopeland.com

Re: Upstream tree for OMFS?

[Stephen Rothwell]

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

Hi Bob,

On Mon, 12 Jul 2010 18:13:07 -0400 Bob Copeland <me@bobcopeland.com> wrote:
>
> Ok - Stephen would you mind including this tree for omfs?
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/bcopeland/omfs.git#for-next

I added this tree today.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgment of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
	Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux 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

Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees.  You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next.  These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc.  The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc.  If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.

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