Hi Stephen,
Please remove my quilt tree
http://ozlabs.org/~rusty/kernel/rr-latest/ from linux-next, and use my
git trees from now on:
git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux.git
Branches:
modules-next
virtio-next
For others: beware that these will rebase, usually once after the merge
window closes (so I can work on a more modern tree), and again just
before it opens (where I squash in fixup patches).
Cheers,
Rusty.
Hi Rusty,
On Tue, 02 Oct 2012 15:56:56 +0930 Rusty Russell <[email protected]> wrote:
>
> Please remove my quilt tree
> http://ozlabs.org/~rusty/kernel/rr-latest/ from linux-next, and use my
> git trees from now on:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux.git
> Branches:
> modules-next
> virtio-next
Done.
> For others: beware that these will rebase, usually once after the merge
> window closes (so I can work on a more modern tree), and again just
> before it opens (where I squash in fixup patches).
The first should not be necessary since everything in these trees should
have been merged by Linus during the merge window, so a merge of -rc1 or
later should be a fast forward (though merging with the tag itself may
produce a real merge). The second can be tricky to pick the right
moment :-)
--
Cheers,
Stephen Rothwell [email protected]
Stephen Rothwell <[email protected]> writes:
> Hi Rusty,
>
> On Tue, 02 Oct 2012 15:56:56 +0930 Rusty Russell <[email protected]> wrote:
>>
>> Please remove my quilt tree
>> http://ozlabs.org/~rusty/kernel/rr-latest/ from linux-next, and use my
>> git trees from now on:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux.git
>> Branches:
>> modules-next
>> virtio-next
>
> Done.
And please add my 'fixes' branch from the same tree.
Thanks,
Rusty.
Hi Rusty,
On Wed, 31 Oct 2012 13:58:15 +1030 Rusty Russell <[email protected]> wrote:
>
> Stephen Rothwell <[email protected]> writes:
> >
> > On Tue, 02 Oct 2012 15:56:56 +0930 Rusty Russell <[email protected]> wrote:
> >>
> >> Please remove my quilt tree
> >> http://ozlabs.org/~rusty/kernel/rr-latest/ from linux-next, and use my
> >> git trees from now on:
> >>
> >> git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux.git
> >> Branches:
> >> modules-next
> >> virtio-next
> >
> > Done.
>
> And please add my 'fixes' branch from the same tree.
Done.
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
[email protected]
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.