Re: [GIT PULL] l10n updates for 2.27.0 round 2

From: Junio C Hamano <gitster@pobox.com>
Date: Jun 1, 2020, 15:45 UTC
Message-ID: <xmqqpnaivlg0.fsf@gitster.c.googlers.com>
In-Reply-To: <CANYiYbH0DzFriPU3AUBfyvADc7OD8r_qjFVp0C2pSVfWk0Zw6Q@mail.gmail.com>

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

Show 25 quoted lines

> 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.