From: Rich Felker <dalias@libc.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Adding linux-sh (arch/sh) to linux-next
Date: Fri, 22 Jul 2016 14:30:06 -0400 [thread overview]
Message-ID: <20160722183006.GA28189@brightrain.aerifal.cx> (raw)
Hi Stephen,
Can you please add the linux-sh tree's for-next branch to be pulled
for linux-next?
git://git.libc.org/linux-sh for-next
Let me know if anything's wrong with how it's set up. I'm new to
linux-next (and still fairly new to arch maintainership) so apologies
if I missed anything. I do plan to move the tree to kernel.org,
hopefully soon, but I'm still waiting on people who promised to sign
my keys so for the time being it's still on libc.org.
Rich
next reply other threads:[~2016-07-22 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 18:30 Rich Felker [this message]
2016-07-24 0:28 ` 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=20160722183006.GA28189@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®