From: Junio C Hamano <gitster@pobox.com>
To: Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: About --staged ang --cached
Date: Wed, 10 Dec 2025 08:06:19 +0900 [thread overview]
Message-ID: <xmqqpl8ni7bo.fsf@gitster.g> (raw)
In-Reply-To: <FD2160CA-DD56-4BDE-92B4-0859C3BD2396@gmail.com> (Lucas Seiki Oshiro's message of "Tue, 9 Dec 2025 16:03:11 -0300")
Lucas Seiki Oshiro <lucasseikioshiro@gmail.com> writes:
> Do you think that it would be relevant to add --staged to the other
> commands just like [2] did to git-diff? Perhaps this is just a personal
> issue, but I find it curious that those commands still have a flag named
> after an obsolete name while newer commands are using --staged.
As long as "Only in the index" aspect of the name is kept, I do not
think the exact phrasing matters all that match. The distinction
between "apply --cached" vs "apply --index" must be expressable even
if you swap "--cached" with something else.
Would it be simpler to remove the label "obsoleted" from the name,
and remove the "--staged" synonym?
next prev parent reply other threads:[~2025-12-09 23:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 19:03 About --staged ang --cached Lucas Seiki Oshiro
2025-12-09 23:06 ` Junio C Hamano [this message]
2025-12-10 2:13 ` Jacob Keller
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=xmqqpl8ni7bo.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=lucasseikioshiro@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).