From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "René Scharfe" <l.s.r@web.de>, "Junio C Hamano" <gitster@pobox.com>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: [BUG?] 'git describe seen'?
Date: Sun, 18 Apr 2021 20:27:03 +0700 [thread overview]
Message-ID: <41392642-d4ff-7a0f-f92c-ea78f4a0b0e1@gmail.com> (raw)
In-Reply-To: <5cb071aa-16d1-8ea8-39e7-a0f5b89cbf3a@web.de>
On 18/04/21 17.26, René Scharfe wrote:
> And vice versa, the fifteen commits that increase the depth of v2.31.1,
> but not of v2.31.0:
>
> 834845142d l10n: de.po: Update German translation for Git v2.31.0
> 408985d301 l10n: pt_PT: add Portuguese translations part 1
> 1369935987 l10n: vi.po(5104t): for git v2.31.0 l10n round 2
> b0adcc311b l10n: es: 2.31.0 round 2
> c21ad4d941 l10n: Add translation team info
> 8c4abfb8be l10n: start Indonesian translation
> 8278f87022 l10n: zh_TW.po: v2.31.0 round 2 (15 untranslated)
> 2f176de687 l10n: bg.po: Updated Bulgarian translation (5104t)
> 1ecef023a9 Merge branch 'fr_next' of github.com:jnavila/git
> 5b888ad949 Merge branch 'master' of github.com:nafmo/git-l10n-sv
> 068cb92300 l10n: fr: v2.31 rnd 2
> f6a7e896b8 l10n: tr: v2.31.0-rc1
> 929dc48e96 l10n: sv.po: Update Swedish translation (5104t0f0u)
> 9b7e82b940 l10n: git.pot: v2.31.0 round 2 (9 new, 8 removed)
> 4dd8469336 Merge branch 'master' of github.com:git/git
>
> That matches the observation above that the depth of v2.31.1 was
> increased by twelve more than the depth of v2.31.0.
Did you mean fifteen commits between v2.31.1 and v2.31.0? If so it's
illogical, because these commits (from git-po workflow) were merged
on rc1-rc2 of v2.31.
--
An old man doll... just what I always wanted! - Clara
prev parent reply other threads:[~2021-04-18 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-17 23:45 [BUG?] 'git describe seen'? Junio C Hamano
2021-04-18 8:21 ` SZEDER Gábor
2021-04-18 9:43 ` SZEDER Gábor
2021-04-18 10:26 ` René Scharfe
2021-04-18 13:27 ` Bagas Sanjaya [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=41392642-d4ff-7a0f-f92c-ea78f4a0b0e1@gmail.com \
--to=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=l.s.r@web.de \
/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;
as well as URLs for NNTP newsgroup(s).