git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiang Xin <worldhello.net@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>,
	"Peter Krefting" <peter@softwolves.pp.se>,
	"Trần Ngọc Quân" <vnwildman@gmail.com>
Cc: Ralf Thielow <ralf.thielow@gmail.com>, Git List <git@vger.kernel.org>
Subject: Re: [PATCH] tag, update-ref: improve description of option "create-reflog"
Date: Sat, 12 Sep 2015 23:07:10 +0800	[thread overview]
Message-ID: <CANYiYbHcmHuvmDmu9aCKiQ20BiPHGj==75BR_x5yscnpFubkdA@mail.gmail.com> (raw)
In-Reply-To: <xmqq613g2990.fsf@gitster.mtv.corp.google.com>

2015-09-12 0:47 GMT+08:00 Junio C Hamano <gitster@pobox.com>:
> Ralf Thielow <ralf.thielow@gmail.com> writes:
>
>> The description of option "create-reflog" is "create_reflog", which
>> is neither a good description, nor a sensible string to translate.
>> Change it to a more meaningful message.
>>
>> Signed-off-by: Ralf Thielow <ralf.thielow@gmail.com>
>> ---
>
> This definitely is an improvement.  I will assume i18n team is OK
> with a change like this this late in the cycle (I see you CC'ed
> Jiang) and will merge before the next -rc.
>

Agree. Those who have already finished this round of l10n
(including sv (Swedish) and vi (Vietnamese)) should update
their translations for this update.


> Thanks.
>
>>  builtin/tag.c        | 2 +-
>>  builtin/update-ref.c | 2 +-
>>  2 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/builtin/tag.c b/builtin/tag.c
>> index cccca99..cba0e22 100644
>> --- a/builtin/tag.c
>> +++ b/builtin/tag.c
>> @@ -606,7 +606,7 @@ int cmd_tag(int argc, const char **argv, const char *prefix)
>>               OPT_STRING('u', "local-user", &keyid, N_("key-id"),
>>                                       N_("use another key to sign the tag")),
>>               OPT__FORCE(&force, N_("replace the tag if exists")),
>> -             OPT_BOOL(0, "create-reflog", &create_reflog, N_("create_reflog")),
>> +             OPT_BOOL(0, "create-reflog", &create_reflog, N_("create a reflog")),
>>
>>               OPT_GROUP(N_("Tag listing options")),
>>               OPT_COLUMN(0, "column", &colopts, N_("show tag list in columns")),
>> diff --git a/builtin/update-ref.c b/builtin/update-ref.c
>> index 04dd00f..7f30d3a 100644
>> --- a/builtin/update-ref.c
>> +++ b/builtin/update-ref.c
>> @@ -365,7 +365,7 @@ int cmd_update_ref(int argc, const char **argv, const char *prefix)
>>                                       N_("update <refname> not the one it points to")),
>>               OPT_BOOL('z', NULL, &end_null, N_("stdin has NUL-terminated arguments")),
>>               OPT_BOOL( 0 , "stdin", &read_stdin, N_("read updates from stdin")),
>> -             OPT_BOOL( 0 , "create-reflog", &create_reflog, N_("create_reflog")),
>> +             OPT_BOOL( 0 , "create-reflog", &create_reflog, N_("create a reflog")),
>>               OPT_END(),
>>       };



-- 
Jiang Xin

      reply	other threads:[~2015-09-12 15:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-11 16:04 [PATCH] tag, update-ref: improve description of option "create-reflog" Ralf Thielow
2015-09-11 16:47 ` Junio C Hamano
2015-09-12 15:07   ` Jiang Xin [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='CANYiYbHcmHuvmDmu9aCKiQ20BiPHGj==75BR_x5yscnpFubkdA@mail.gmail.com' \
    --to=worldhello.net@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peter@softwolves.pp.se \
    --cc=ralf.thielow@gmail.com \
    --cc=vnwildman@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.
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).