mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <>
To: "brian m. carlson" <>
Cc:, "Jean-Noël Avila" <>
Subject: Re: [PATCH] po: add missing letter for French message
Date: Thu, 27 Aug 2020 16:04:02 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (brian m. carlson's message of "Thu, 27 Aug 2020 22:35:27 +0000")

"brian m. carlson" <> writes:

> Add the missing "e" in "de".  While it is possible in French to omit it,
> that only occurs with an apostrophe and only when the next word starts
> with a vowel or mute h, which is not the case here.
> Signed-off-by: brian m. carlson <>
> ---
> I noticed this the other day when trying to delete a remote branch that
> I'd already deleted.  I'm not sure what the preferred approach is for
> this, whether Junio should pick it up or whether Jean-Noël will want to
> incorporate it first, but I've CC'd both so y'all can fight it out.

Unless it is in the pre-release period (in which case I'd prefer not
to touch po/ myself at all, to give i18n/l10n teams a stable base to
work from), I can take it dircetly as long as somebody from the l10n
team for the language gives an Ack, as I cannot read most of the
files under po/ directory.


>  po/fr.po | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> diff --git a/po/fr.po b/po/fr.po
> index d20fc440ab..75b1e75f6a 100644
> --- a/po/fr.po
> +++ b/po/fr.po
> @@ -6503,7 +6503,7 @@ msgstr "'%s' ne peut pas être résolue comme une branche"
>  #: remote.c:1088
>  #, c-format
>  msgid "unable to delete '%s': remote ref does not exist"
> -msgstr "suppression d '%s' impossible : la référence distante n'existe pas"
> +msgstr "suppression de '%s' impossible : la référence distante n'existe pas"
>  #: remote.c:1100
>  #, c-format

  reply	other threads:[~2020-08-27 23:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-27 22:35 [PATCH] po: add missing letter for French message brian m. carlson
2020-08-27 23:04 ` Junio C Hamano [this message]
2020-08-28 15:53   ` Jean-Noël AVILA
2020-08-28 21:00     ` Junio C Hamano

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:

  List information:

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

  git send-email \ \ \ \ \ \

* 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

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