From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] arch/h8300 for 4.2
Date: Thu, 25 Jun 2015 15:49:41 +0900 [thread overview]
Message-ID: <87si9gz3i2.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <CA+55aFzMJ5Jh5L8yorsNo-PswDHyizAUFHAwFg6bzkJ98SagPg@mail.gmail.com>
On Thu, 25 Jun 2015 01:03:05 +0900,
Linus Torvalds wrote:
>
> On Tue, Jun 23, 2015 at 9:17 AM, Yoshinori Sato
> <ysato@users.sourceforge.jp> wrote:
> >
> > Could you pull this tree?
> > git://git.sourceforge.jp/gitroot/uclinux-h8/linux.git for-4.2
>
> Welcome back for the h8300 tree... Well, almost:
>
> I was going to pull it, but then noticed that it's at a random public
> site, and unsigned.
>
> So there is nothing wrong with the content, but I do not want to pull
> from random untrusted sites without having a signed tag. So I'd ask
> you to create a signed tag ("git tag -s") and ask me to pull that
> instead, ok?
OK.
Please pull signed tag.
git://git.sourceforge.jp/gitroot/uclinux-h8/linux.git for-4.2
> Are you still DC21AAD1, or do you have a newer pgp key? Maybe
> something bigger than 1024 bits?
DC21AAD1 is active. but it too shortly.
I created new key 0B28399C and signed tag.
> Also, would you mind adding a small explanation (maybe in the signed
> key, or maybe just in the new pull request) about what has changed in
> the h8300 tree (and maybe support)? I'm assuming this is not just
> resurrecting the old code, but is a new cleaned-up version?
It's being rewritten overall.
A remaining old cord is few hundreds lines.
> Thanks,
> Linus
Thanks.
--
Yoshinori Sato
<ysato@users.sourceforge.jp>
prev parent reply other threads:[~2015-06-25 6:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 16:17 [GIT PULL] arch/h8300 for 4.2 Yoshinori Sato
2015-06-24 16:03 ` Linus Torvalds
2015-06-25 6:49 ` Yoshinori Sato [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=87si9gz3i2.wl-ysato@users.sourceforge.jp \
--to=ysato@users.sourceforge.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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