From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jiri Kosina <jkosina@suse•cz>
Cc: linux-next@vger•kernel.org, linux-doc@vger•kernel.org,
Randy Dunlap <rdunlap@infradead•org>
Subject: Re: linux-next tree addition request -- doc.git
Date: Tue, 30 Sep 2014 08:16:35 +1000 [thread overview]
Message-ID: <20140930081635.6ca54fd3@canb.auug.org.au> (raw)
In-Reply-To: <alpine.LNX.2.00.1409261132330.22196@pobox.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1315 bytes --]
Hi Jiri,
On Fri, 26 Sep 2014 11:37:06 +0200 (CEST) Jiri Kosina <jkosina@suse•cz> wrote:
>
> as a followup to Randy stepping down as a documentation maintainer [1],
> could you please add
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jikos/doc.git#for-next
>
> to the pile that gets pulled into linux-next?
>
> Thanks.
>
> [1] d671e42457e1fef70ad0df07084207078633a9e8
Added from today. I also removed Randy's patch series.
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-09-29 22:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 9:37 linux-next tree addition request -- doc.git Jiri Kosina
2014-09-26 10:41 ` Sedat Dilek
2014-09-26 10:52 ` Jiri Kosina
2014-09-26 11:02 ` Stephen Rothwell
2014-09-26 11:04 ` Jiri Kosina
2014-09-29 22:16 ` Stephen Rothwell [this message]
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=20140930081635.6ca54fd3@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=jkosina@suse$(echo .)cz \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rdunlap@infradead$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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