From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jiri Kosina <jikos@kernel•org>
Cc: linux-next@vger•kernel.org
Subject: Re: Please (re)add trivial.git to linux-next
Date: Wed, 18 Mar 2020 21:22:06 +1100 [thread overview]
Message-ID: <20200318212206.4ed15ffe@canb.auug.org.au> (raw)
In-Reply-To: <nycvar.YFH.7.76.2003172149190.19500@cbobk.fhfr.pm>
[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]
Hi Jiri,
On Tue, 17 Mar 2020 21:49:34 +0100 (CET) Jiri Kosina <jikos@kernel•org> wrote:
>
> On Tue, 17 Mar 2020, Jiri Kosina wrote:
>
> > I will try to revive trivial.git which I've been neglecting for quite a
> > long time.
> >
> > I've already pushed first part of the queue to kernel.org; could you
> > please readd
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial.git/
>
> ... more precisely 'for-next' branch of that tree.
Added from today.
Thanks for adding your subsystem tree as a participant of linux-next. As
you may know, this is not a judgement 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: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-03-18 10:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 20:07 Please (re)add trivial.git to linux-next Jiri Kosina
2020-03-17 20:49 ` Jiri Kosina
2020-03-18 10:22 ` 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=20200318212206.4ed15ffe@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=jikos@kernel$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.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