All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Rast <trast@inf.ethz.ch>
To: Junio C Hamano <gitster@pobox.com>, Jonathan Nieder <jrnieder@gmail.com>
Cc: "Jiang Xin" <worldhello.net@gmail.com>,
	"Git List" <git@vger.kernel.org>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: Re: [PATCH v3 5/7] i18n: am: mark more strings for translation
Date: Wed, 25 Jul 2012 08:38:26 +0200	[thread overview]
Message-ID: <871uk0ny59.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <7vwr1sevpu.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Tue, 24 Jul 2012 13:43:25 -0700")

Junio C Hamano <gitster@pobox.com> writes:

> Jonathan Nieder <jrnieder@gmail.com> writes:
>
>> Before this patch, it says
>>
>> 	The --binary option has been a no-op for a long time, and ...
>>
>> After the patch, it says
>>
>> 	The -b option has been a no-op for a long time, and ...
>>
>> Intentional?  That may be a good change or a bad one (I haven't
>> thought clearly about it), but it seems at least worth mentioning.
>> Cc-ing Thomas in case he has advice.
>
> If we really care we could printf $1, but I think we usually do
>
> 	The -b/--binary option has been...
>
> in a case like this, especially in codepaths that no longer has an
> easy access to $1 after parsing the command line but knows that
> either one of them is given from the parse result, and that would be
> an appropriate solution for this particular one as well.

Yes.  The original plan was to free up -b, but since we don't need
--binary any more either, it's better if we can get rid of it the same
way.

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

  reply	other threads:[~2012-07-25  6:38 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-24  6:59 [PATCH v3 0/7] i18n for git-am, git-rebase and git-merge Jiang Xin
2012-07-24  6:59 ` [PATCH v3 1/7] i18n: New keywords for xgettext extraction from sh Jiang Xin
2012-07-24  9:38   ` Stefano Lattarini
2012-07-24 17:46   ` Jonathan Nieder
2012-07-24  6:59 ` [PATCH v3 2/7] i18n: rebase: mark strings for translation Jiang Xin
2012-07-24  9:43   ` Stefano Lattarini
2012-07-24 18:01   ` Jonathan Nieder
2012-07-24 18:57     ` Junio C Hamano
2012-07-24 22:49     ` Jiang Xin
2012-07-24  6:59 ` [PATCH v3 3/7] i18n: Rewrite gettext messages start with dash Jiang Xin
2012-07-24  9:44   ` Stefano Lattarini
2012-07-24  6:59 ` [PATCH v3 4/7] Remove obsolete LONG_USAGE which breaks xgettext Jiang Xin
2012-07-24 18:08   ` Jonathan Nieder
2012-07-24 19:07     ` Junio C Hamano
2012-07-24  6:59 ` [PATCH v3 5/7] i18n: am: mark more strings for translation Jiang Xin
2012-07-24 18:16   ` Jonathan Nieder
2012-07-24 20:43     ` Junio C Hamano
2012-07-25  6:38       ` Thomas Rast [this message]
2012-07-24 23:00     ` Jiang Xin
2012-07-24  6:59 ` [PATCH v3 6/7] Remove unused and bad gettext block from git-am Jiang Xin
2012-07-24 18:27   ` Jonathan Nieder
2012-07-24 20:40     ` Junio C Hamano
2012-07-24 21:16     ` Martin von Zweigbergk
2012-07-24 21:21       ` Junio C Hamano
2012-07-24 21:25       ` Jonathan Nieder
2012-07-24 22:18         ` Junio C Hamano
2012-07-24  6:59 ` [PATCH v3 7/7] i18n: merge-recursive: mark strings for translation Jiang Xin
2012-07-24  9:47   ` Stefano Lattarini

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=871uk0ny59.fsf@thomas.inf.ethz.ch \
    --to=trast@inf.ethz.ch \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.com \
    --cc=pclouds@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.