Re: [PATCH v3 00/10] commit-graph write: progress output improvements

From: Eric Sunshine <sunshine@sunshineco.com>
Date: Nov 22, 2018, 18:59 UTC
Message-ID: <CAPig+cRCrbnoQoX72bmRcuYVP9b8W0gfrg0tL4kmuKfsYGa3bA@mail.gmail.com>
In-Reply-To: <20181122132823.9883-1-avarab@gmail.com>

On Thu, Nov 22, 2018 at 8:28 AM Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:

> Range-diff:
> By the way, is there any way to....
> Pass the equivalent of "git range-diff origin/master topic-2 topic-3"
> to git-format-patch?

git-range-diff documentations says that the three-argument form:

    git range-diff <base> <rev1> <rev2>

is equivalent to passing two ranges:

    git range-diff <base>..<rev1> <base>..<rev2>

git-format-patch synopsis shows:

    git format-patch --range-diff=<previous> <rev-range>

where <rev-range> is the range of commits to format, and <previous> can be a range specifying the previous version, so:

    git format-patch --range-diff=<base>..<rev1> <base>..<rev2>

should do what you ask.

However, since the two versions in your example both derive from origin/master, you should be able to get by with the simpler:

    git format-patch --range-diff=<rev1> <base>..<rev2>

which, if you were running git-range-diff manually, would be the equivalent of:

    git range-diff <rev1>...<rev2>

for which the range-diff machinery figures out the common base (origin/master) automatically.