From: Junio C Hamano <gitster@pobox.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Git List Mailing <git@vger.kernel.org>
Subject: Re: RFC: Using '--no-output-indicator-old' to only show new state
Date: Thu, 10 Mar 2022 13:26:29 -0800 [thread overview]
Message-ID: <xmqqfsnpcxdm.fsf@gitster.g> (raw)
In-Reply-To: <CAHk-=wg+n_-btzoyMqnDYsJxFYAyUh0Kb=TkpS8RiD_h3G=_cA@mail.gmail.com> (Linus Torvalds's message of "Thu, 10 Mar 2022 12:40:06 -0800")
Linus Torvalds <torvalds@linux-foundation.org> writes:
> So "--new/old"? "--pre/post"?
>
> Or it could be something random, and tie it with the existing "-U"
> option, where "-U+" would be "positive side only", and "-U5-" would be
> "5 context lines, negative side only". Very dense and convenient,
> maybe not all that intuitive?
I often use -W and the above would give us a natural extension, but
I agree that is a bit too dense and totally unintuitive. As we use
parse-options for patch output formatting options, my pick would be
"--new-only" vs "--old-only" (if there were existing options that
has new/old in their names, "--preimage-only" and "--postimage-only"
would also work, but that's much longer), and let the option parser
accept unique abbreviations like "--new" and "--old".
next prev parent reply other threads:[~2022-03-10 21:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 19:40 RFC: Using '--no-output-indicator-old' to only show new state Linus Torvalds
2022-03-10 20:13 ` Junio C Hamano
2022-03-10 20:40 ` Linus Torvalds
2022-03-10 21:26 ` Junio C Hamano [this message]
2022-03-10 22:13 ` Linus Torvalds
2022-03-11 0:01 ` Linus Torvalds
2022-03-11 7:48 ` Ævar Arnfjörð Bjarmason
2022-03-11 9:45 ` [PATCH] parse-options: add per-option flag to stop abbreviation Ævar Arnfjörð Bjarmason
2022-03-11 18:44 ` Linus Torvalds
2022-03-11 19:15 ` RFC: Using '--no-output-indicator-old' to only show new state Linus Torvalds
2022-03-11 19:42 ` Konstantin Ryabitsev
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=xmqqfsnpcxdm.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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.