git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 12:13:44 -0800	[thread overview]
Message-ID: <xmqqo82dd0qv.fsf@gitster.g> (raw)
In-Reply-To: <CAHk-=wgh8emJn-+FtxN=m_SCPiP6cGKHU-5ozzV9tWBMxn+xcA@mail.gmail.com> (Linus Torvalds's message of "Thu, 10 Mar 2022 11:40:50 -0800")

Linus Torvalds <torvalds@linux-foundation.org> writes:

> So after another round of doing
>
>      git diff | grep -v '^-'
>
> to just show what the end result of a patch is, I decided that there
> has to be a better way.
>
> Of course, to normal people, that "better way" is probably some GUI
> tool that shows diffs as "before/after" in two different frames next
> to each other, but I'm a grumpy old man ("Get off my lawn") and I do
> everything but read my email in a standard text-only terminal.

Sounds like the "apply --no-add" in the opposite direction ;-) I
would find it handy myself, too, though I tend to read my patches
after applying to my tree so the postimage is usually an invocation
of "less" away for me.

I do not think it is a bad idea to have an option to give only the
postimage and another option to give only the preimage.  It would
also trivially allow people to show the side-by-side diff in GUI.

  reply	other threads:[~2022-03-10 20:13 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 [this message]
2022-03-10 20:40   ` Linus Torvalds
2022-03-10 21:26     ` Junio C Hamano
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=xmqqo82dd0qv.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 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).