Re: [PATCH v4 00/35] protocol version 2

From: Junio C Hamano <gitster@pobox.com>
Date: Mar 1, 2018, 20:59 UTC
Message-ID: <xmqqbmg7fr5s.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <20180301191629.GA241240@google.com>

Brandon Williams <bmwill@google.com> writes:

> I've tried to keep building on the same base that I started with when
> sending out a new version of series, mostly because I thought it was
> easier to see what was different between rounds.

Yes. It indeed is easier to see the evolution if the series does not get rebased needlessly.

> I can, in the future, try to remember to put the commit its based on.
> Do we have any sort of guidance about the best practice here?

I recall we taught a new "--base" option to "format-patch" not too long ago, so one way to do so may be:

    $ git format-patch --cover-letter --base=v2.16.0-rc0 master..bw/protocol-v2
    $ tail -4 0000-cover*.txt
    base-commit: 1eaabe34fc6f486367a176207420378f587d3b48
    --
    2.16.2-345-g7e31236f65

perhaps?