From: "Jean-Noël AVILA" <jn.avila@free.fr>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>,
"Bagas Sanjaya" <bagasdotme@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: ja/i18n-common-messages
Date: Sun, 06 Feb 2022 11:03:52 +0100 [thread overview]
Message-ID: <6114905.tHSIdXRuFm@cayenne> (raw)
In-Reply-To: <032852b5-0cb3-4515-592c-9433930946f3@gmail.com>
On Sunday, 6 February 2022 09:12:08 CET Bagas Sanjaya wrote:
> On 05/02/22 19.18, Jean-Noël AVILA wrote:
> > Bad news: this implementation is already crippled. For instance, calling `git
> > commit --fixup -m -c` would first bring up:
> > "options '-c' and '--fixup' cannot be used together"
> > Then remove --fixup and you get
> > "options '-m' and '-c' cannot be used together"
> >
> > This is because (according to the code, I don't know if it's really what's
> > wanted) the real logic is
> > Exclusive ("-C", "-c", "-F", Or("--fixup", "-m"))
>
> I read that your intended logic as 'options "-c", "-m", and '--fixup' cannot
> be used together', right?
>
>
In such case, in a perfect UI, I would expect more something along
"option '-C' cannot be used with '--fixup' and '-m'"
next prev parent reply other threads:[~2022-02-06 10:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 5:22 What's cooking in git.git (Feb 2022, #01; Thu, 3) Junio C Hamano
2022-02-04 7:00 ` Eric Sunshine
2022-02-05 8:00 ` Junio C Hamano
2022-02-04 8:13 ` Opinions on merging questions (Was: What's cooking in git.git (Feb 2022, #01; Thu, 3)) Elijah Newren
2022-02-04 11:20 ` en/remerge-diff (was: Opinions on merging questions (Was: What's cooking in git.git (Feb 2022, #01; Thu, 3))) Ævar Arnfjörð Bjarmason
2022-02-04 16:42 ` en/remerge-diff Junio C Hamano
2022-02-06 11:41 ` Opinions on merging questions (Was: What's cooking in git.git (Feb 2022, #01; Thu, 3)) Eric Sunshine
2022-02-09 14:57 ` Derrick Stolee
2022-02-07 14:11 ` Phillip Wood
2022-02-04 11:25 ` jc/doc-log-messages (was: " Ævar Arnfjörð Bjarmason
2022-02-04 12:23 ` rj/receive-pack-abort-upon-disconnect " Ævar Arnfjörð Bjarmason
2022-02-04 12:25 ` cb/clear-quarantine-early-on-all-ref-update-errors " Ævar Arnfjörð Bjarmason
2022-02-04 16:45 ` cb/clear-quarantine-early-on-all-ref-update-errors Junio C Hamano
2022-02-04 12:29 ` ja/i18n-common-messages (was: What's cooking in git.git (Feb 2022, #01; Thu, 3)) Ævar Arnfjörð Bjarmason
2022-02-04 16:56 ` ja/i18n-common-messages Junio C Hamano
2022-02-05 12:18 ` ja/i18n-common-messages Jean-Noël AVILA
2022-02-06 8:12 ` ja/i18n-common-messages Bagas Sanjaya
2022-02-06 10:03 ` Jean-Noël AVILA [this message]
2022-02-04 12:31 ` ps/avoid-unnecessary-hook-invocation-with-packed-refs (was: What's cooking in git.git (Feb 2022, #01; Thu, 3)) Ævar Arnfjörð Bjarmason
2022-02-04 12:36 ` ab/ambiguous-object-name " Ævar Arnfjörð Bjarmason
2022-02-04 13:05 ` tl/ls-tree-oid-only " Ævar Arnfjörð Bjarmason
2022-02-04 13:11 ` ab/only-single-progress-at-once " Ævar Arnfjörð Bjarmason
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=6114905.tHSIdXRuFm@cayenne \
--to=jn.avila@free.fr \
--cc=avarab@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.