From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <ttaylorr@github.com>
Cc: ZheNing Hu via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Denton Liu <liu.denton@gmail.com>, Taylor Blau <me@ttaylorr.com>,
ZheNing Hu <adlternative@gmail.com>
Subject: Re: [PATCH] [GSOC][RFC] format-patch: pass --right-only to range-diff
Date: Fri, 12 Mar 2021 13:55:07 -0800 [thread overview]
Message-ID: <xmqq1rck6nr8.fsf@gitster.g> (raw)
In-Reply-To: <YEaGbn5rU3pU7/q5@nand.local> (Taylor Blau's message of "Mon, 8 Mar 2021 15:18:04 -0500")
Taylor Blau <ttaylorr@github.com> writes:
> Note that I think (and Johannes--cc'd--could confirm) that what you want
> is '--left-only' to discard rebased changes from the upstream branch:
Does that mean range-diff got --left-only and --right-only
backwards? IOW, doesn't
$ git log --left-only A...B
show what is shown in "git log B..A", and if so, shouldn't
$ git range-diff --left-only A...B
which is a synonym for
$ git range-diff B..A A..B
also give commits in the B..A range?
Puzzled....
next prev parent reply other threads:[~2021-03-12 21:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 6:57 [PATCH] [GSOC][RFC] format-patch: pass --right-only to range-diff ZheNing Hu via GitGitGadget
2021-03-08 20:18 ` Taylor Blau
2021-03-09 7:28 ` ZheNing Hu
2021-03-12 21:55 ` Junio C Hamano [this message]
2021-03-12 22:09 ` Junio C Hamano
2021-03-09 8:33 ` [PATCH v2] [GSOC][RFC] format-patch: pass --left-only " ZheNing Hu via GitGitGadget
2021-03-09 9:00 ` Eric Sunshine
2021-03-09 9:35 ` ZheNing Hu
2021-03-09 10:28 ` [PATCH v3] " ZheNing Hu via GitGitGadget
2021-03-12 22:50 ` Junio C Hamano
2021-03-13 4:01 ` ZheNing Hu
2021-03-13 23:23 ` Junio C Hamano
2021-03-14 2:16 ` ZheNing Hu
2021-03-14 2:37 ` ZheNing Hu
2021-03-14 2:41 ` ZheNing Hu
2021-03-14 8:10 ` [PATCH v4] [GSOC] " ZheNing Hu via GitGitGadget
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=xmqq1rck6nr8.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=adlternative@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=liu.denton@gmail.com \
--cc=me@ttaylorr.com \
--cc=ttaylorr@github.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.