All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] arch/h8300 update
Date: Sun, 06 Jan 2019 21:37:36 +0900	[thread overview]
Message-ID: <877efiklm7.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <CAHk-=wiuzkhzr8SJXvy7NHGS+3XyQk1VUAg2s=-xE_BSqCCoXg@mail.gmail.com>

On Sun, 06 Jan 2019 04:40:55 +0900,
Linus Torvalds wrote:
> 
> On Sat, Jan 5, 2019 at 1:34 AM Yoshinori Sato
> <ysato@users.sourceforge.jp> wrote:
> >
> >   git://git.sourceforge.jp/gitroot/uclinux-h8/linux.git tags/for-4.21
> 
> New signing key?

Yes. My previous key was made more than 10 years ago, and it is not strong enough.

> That's ok, but please sign it with your old one unless there's some
> major reason you can't (ie "oops, I've lost the old one").
> 
> And yes, I see that the new key is nice and much stronger, but it
> would still be nice to have the signature chain to your old one.

I intended to do so, but I will check it.
Thanks.

>               Linus

-- 
Yosinori Sato

  reply	other threads:[~2019-01-06 12:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-05  9:34 [GIT PULL] arch/h8300 update Yoshinori Sato
2019-01-05 19:40 ` Linus Torvalds
2019-01-06 12:37   ` Yoshinori Sato [this message]
2019-01-05 20:20 ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2019-07-17  7:59 Yoshinori Sato
2019-07-17 16:37 ` Linus Torvalds
2019-07-17 16:50 ` pr-tracker-bot
2018-08-21  9:49 Yoshinori Sato
2018-08-21 20:33 ` Linus Torvalds
2018-08-22 12:48   ` Yoshinori Sato
2018-08-22 13:36     ` Linus Torvalds
2018-08-22 14:04       ` Linus Torvalds
2018-08-23 13:46         ` Yoshinori Sato

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=877efiklm7.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.