From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Richard Weinberger <richard@nod.at>
Cc: linux-next@vger.kernel.org
Subject: Re: Please add UML to linux-next
Date: Wed, 25 Mar 2015 17:07:24 +1100 [thread overview]
Message-ID: <20150325170724.33730ad5@canb.auug.org.au> (raw)
In-Reply-To: <5511DE72.6040109@nod.at>
[-- Attachment #1: Type: text/plain, Size: 554 bytes --]
Hi Richard,
On Tue, 24 Mar 2015 23:00:18 +0100 Richard Weinberger <richard@nod.at> wrote:
>
> can you please add the following tree to linux-next?
> git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml.git linux-next
Unfortunately, that "linux-next" is a tag and I am not set up to fetch
from tags easily, Could I trouble you to make that a branch instead,
please?
(I notice that the tag is currently sitting on v4.0-rc5, so there is
nothing in the uml tree yet.)
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-03-25 6:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 22:00 Please add UML to linux-next Richard Weinberger
2015-03-25 6:07 ` Stephen Rothwell [this message]
2015-03-26 0:06 ` Stephen Rothwell
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=20150325170724.33730ad5@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-next@vger.kernel.org \
--cc=richard@nod.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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