From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Sudheer D <Sudheer.D@ibm.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git diff without intermediate commits
Date: Thu, 09 Mar 2023 09:13:48 -0800 [thread overview]
Message-ID: <xmqqwn3pc0fn.fsf@gitster.g> (raw)
In-Reply-To: <ZAl7JI3FZdUgrvkq@coredump.intra.peff.net> (Jeff King's message of "Thu, 9 Mar 2023 01:22:28 -0500")
Jeff King <peff@peff.net> writes:
> You can try something like:
> ...
> which will work sometimes,
Yup, that is how I would do the comparison, if I cannot undo these
"pointless merges from the upstream".
> but I don't think it would be a good idea to
> build a feature around it.
Probably.
Thanks.
prev parent reply other threads:[~2023-03-09 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 5:52 git diff without intermediate commits Sudheer D
2023-03-09 6:22 ` Jeff King
2023-03-09 17:13 ` Junio C Hamano [this message]
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=xmqqwn3pc0fn.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Sudheer.D@ibm.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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.