git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jiang Xin <worldhello.net@gmail.com>
Cc: "Git List" <git@vger.kernel.org>,
	"Alessandro Menti" <alessandro.menti@alessandromenti.it>,
	"Alexander Shopov" <ash@kambanaria.org>,
	"Christopher Diaz Riveros" <christopher.diaz.riv@gmail.com>,
	"Emir Sarı" <bitigchi@me.com>, "Jan Engelhardt" <jengelh@inai.de>,
	"Jean-Noël Avila" <jn.avila@free.fr>,
	"Jordi Mas" <jmas@softcatala.org>,
	"Matthias Rüster" <matthias.ruester@gmail.com>,
	"Peter Krefting" <peter@softwolves.pp.se>,
	"Tran Ngoc Quan" <vnwildman@gmail.com>,
	"Yi-Jyun Pan" <pan93412@gmail.com>
Subject: Re: [GIT PULL] l10n updates for 2.27.0 round 2
Date: Mon, 01 Jun 2020 08:45:51 -0700	[thread overview]
Message-ID: <xmqqpnaivlg0.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <CANYiYbH0DzFriPU3AUBfyvADc7OD8r_qjFVp0C2pSVfWk0Zw6Q@mail.gmail.com> (Jiang Xin's message of "Mon, 1 Jun 2020 15:35:22 +0800")

Jiang Xin <worldhello.net@gmail.com> writes:

> Junio C Hamano <gitster@pobox.com> 于2020年6月1日周一 上午2:15写道:
>>
>> Jiang Xin <worldhello.net@gmail.com> writes:
>>
>> > Hi Junio,
>> >
>> > Please pull the following l10n updates for Git 2.27.0.
>> >
>> > The following changes since commit 2d5e9f31ac46017895ce6a183467037d29ceb9d3:
>> >
>> >   Git 2.27-rc2 (2020-05-26 09:38:13 -0700)
>> >
>> > are available in the Git repository at:
>> >
>> >   git@github.com:git-l10n/git-po.git tags/l10n-2.27.0-rnd2
>> >
>> > for you to fetch changes up to cb26198ec6b3fa0bc58d210ea0338f4e972f9f50:
>> >
>> >   Merge branch 'master' of github.com:ruester/git-po-de (2020-05-30 11:26:53 +0800)
>>
>> Thanks.  Swapped GPG key recently?
>
> My pgp key has expired on April 6th, so I generated a new one.  Which
> is the best practice? Edit the old pgp key to extend the expiry time
> or generate a new pgp key?

Either is OK; it's not as if we've met in person and exchanged our
keys (I tend to extend the expiration date, as that key would be
still recognisable by those who have been trusting that key; you can
do the similar chaining of trust by signing the new key with the old
key before starting to use the new one, I suppose).

Thanks.

      reply	other threads:[~2020-06-01 15:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-31  5:17 [GIT PULL] l10n updates for 2.27.0 round 2 Jiang Xin
2020-05-31 18:15 ` Junio C Hamano
2020-06-01  7:35   ` Jiang Xin
2020-06-01 15:45     ` Junio C Hamano [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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqpnaivlg0.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=alessandro.menti@alessandromenti.it \
    --cc=ash@kambanaria.org \
    --cc=bitigchi@me.com \
    --cc=christopher.diaz.riv@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jengelh@inai.de \
    --cc=jmas@softcatala.org \
    --cc=jn.avila@free.fr \
    --cc=matthias.ruester@gmail.com \
    --cc=pan93412@gmail.com \
    --cc=peter@softwolves.pp.se \
    --cc=vnwildman@gmail.com \
    --cc=worldhello.net@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).