Re: [GIT PULL] Btrfs for linux-next

* Re: [GIT PULL] Btrfs for linux-next
       [not found] <20120930115258.GA13506@shiny>
@ 2012-10-01  8:15 ` Stephen Rothwell
  2012-10-02  1:36   ` Chris Mason
  0 siblings, 1 reply; 4+ messages in thread
From: Stephen Rothwell @ 2012-10-01  8:15 UTC (permalink / raw)
  To: Chris Mason; +Cc: linux-next

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

Hi Chris,

On Sun, 30 Sep 2012 07:52:58 -0400 Chris Mason <chris.mason@fusionio.com> wrote:
>
> This is our large queue of changes for linux-next.  They vary from bug
> fixes to huge optimizations.  It also includes a new disk format feature
> from suse to remove a restriction on the number of hardlinks to a single
> file in a single dir.
> 
> I tested against linux-next on Friday, it was a clean merge and passes
> xfstests.
> 
> Just let me know if there are any problems, thanks!  The changes are in
> my next branch
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git next

I added your tree today, but as you have seen it broke :-(

Normally I would just go back to the previous days tree, but this is your
first day, so I just dropped it.  I will try again tomorrow (hopefully it
will be fixed by then).

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: 836 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread