Re: [RFC PATCH 4/5] format-patch: teach --range-diff to respect -v/--reroll-count
- From
Stefan Beller <sbeller@google.com>
- Date
- May 30, 2018, 19:03 UTC
- Message-ID
- <CAGZ79kZ2MKpjwwx0+ZsPZ9bFu_ersPJ=kKPYWRmWYjJ8yoVhuA@mail.gmail.com>
- In-Reply-To
- <20180530080325.37520-5-sunshine@sunshineco.com>
On Wed, May 30, 2018 at 1:03 AM, Eric Sunshine <sunshine@sunshineco.com> wrote:
> The --range-diff option introduces the embedded range-diff generically
> as "Changes since previous version:", however, we can do better when
> --reroll-count is specified by emitting "Changes since v{n}:" instead.A very similar option that I used before finding reroll count is --subject-prefix I still use that for RFC/WIP tags, but I sometimes used it with "PATCHv2" as an argument, too.
Would we want to extend the niceties of this patch to that workflow?
Unrelated to this patch: how does this series cope with range diffs that are not in commit-ish but patches on the file system?