From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: git@vger.kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Stefan Beller" <sbeller@google.com>
Subject: Re: [RFC PATCH 0/5] format-patch: automate cover letter range-diff
Date: Tue, 17 Jul 2018 12:04:58 +0200 (DST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1807171204080.71@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <20180530080325.37520-1-sunshine@sunshineco.com>
Hi Eric,
On Wed, 30 May 2018, Eric Sunshine wrote:
> Dscho recently implemented a 'tbdiff' replacement as a Git builtin named
> git-branch-diff[1] which computes differences between two versions of a
> patch series. Such a diff can be a useful aid for reviewers when
> inserted into a cover letter. However, doing so requires manual
> generation (invoking git-branch-diff) and copy/pasting the result into
> the cover letter.
>
> This series fully automates the process by adding a --range-diff option
> to git-format-patch.
Nice!
> It is RFC for a couple reasons:
>
> * The final name for the 'tbdiff' replacement has not yet been nailed
> down. The name git-branch-diff is moribund[2]; Dscho favors merging
> the functionality into git-branch as a new --diff option[3]; others
> prefer a standalone command named git-range-diff or
> git-series-diff[4] or similar.
I think this has been settled now: range-diff it is.
> * I have some ideas for future enhancements and want to be careful not
> to lock in a UI which doesn't mesh well with them (though I think the
> current UI turned out reasonably well). First, I foresee a
> complementary --interdiff option for inserting an interdiff-style diff
> for cases when that style is easier to read or simply more
> appropriate. Second, although the current patch series only supports
> --range-diff for the cover letter, some people insert interdiff- or
> tbdiff-style diffs (indented) into the commentary section of
> standalone patches. Although this often makes for a noisy mess, it is
> periodically useful.
Sure.
> This series is built atop js/branch-diff in 'pu'.
>
> [1]: https://public-inbox.org/git/cover.1525448066.git.johannes.schindelin@gmx.de/
> [2]: https://public-inbox.org/git/nycvar.QRO.7.76.6.1805061401260.77@tvgsbejvaqbjf.bet/
> [3]: https://public-inbox.org/git/nycvar.QRO.7.76.6.1805062155120.77@tvgsbejvaqbjf.bet/
> [4]: https://public-inbox.org/git/xmqqin7gzbkb.fsf@gitster-ct.c.googlers.com/
>
> Eric Sunshine (5):
> format-patch: allow additional generated content in
> make_cover_letter()
> format-patch: add --range-diff option to embed diff in cover letter
> format-patch: extend --range-diff to accept revision range
> format-patch: teach --range-diff to respect -v/--reroll-count
> format-patch: add --creation-weight tweak for --range-diff
>
> Documentation/git-format-patch.txt | 18 +++++
> builtin/log.c | 119 ++++++++++++++++++++++++-----
> t/t7910-branch-diff.sh | 16 ++++
> 3 files changed, 132 insertions(+), 21 deletions(-)
>
> --
> 2.17.1.1235.ge295dfb56e
Thanks!
Dscho
next prev parent reply other threads:[~2018-07-17 10:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 8:03 [RFC PATCH 0/5] format-patch: automate cover letter range-diff Eric Sunshine
2018-05-30 8:03 ` [RFC PATCH 1/5] format-patch: allow additional generated content in make_cover_letter() Eric Sunshine
2018-07-17 10:15 ` Johannes Schindelin
2018-07-17 10:24 ` Eric Sunshine
2018-05-30 8:03 ` [RFC PATCH 2/5] format-patch: add --range-diff option to embed diff in cover letter Eric Sunshine
2018-07-17 10:30 ` Johannes Schindelin
2018-07-17 10:49 ` Eric Sunshine
2018-07-26 10:55 ` Johannes Schindelin
2018-07-26 20:57 ` Eric Sunshine
2018-07-27 15:18 ` Johannes Schindelin
2018-05-30 8:03 ` [RFC PATCH 3/5] format-patch: extend --range-diff to accept revision range Eric Sunshine
2018-05-30 18:58 ` Stefan Beller
2018-05-30 20:26 ` Eric Sunshine
2018-07-17 10:44 ` Johannes Schindelin
2018-07-17 10:50 ` Eric Sunshine
2018-05-30 8:03 ` [RFC PATCH 4/5] format-patch: teach --range-diff to respect -v/--reroll-count Eric Sunshine
2018-05-30 19:03 ` Stefan Beller
2018-05-30 20:44 ` Eric Sunshine
2018-05-30 21:03 ` Stefan Beller
2018-05-30 21:14 ` Eric Sunshine
2018-05-30 8:03 ` [RFC PATCH 5/5] format-patch: add --creation-weight tweak for --range-diff Eric Sunshine
2018-07-17 11:00 ` Johannes Schindelin
2018-05-30 9:25 ` [RFC PATCH 0/5] format-patch: automate cover letter range-diff Ævar Arnfjörð Bjarmason
2018-06-06 19:16 ` Duy Nguyen
2018-06-07 8:34 ` Eric Sunshine
2018-06-07 15:09 ` Duy Nguyen
2018-07-17 10:04 ` Johannes Schindelin [this message]
2018-07-26 12:03 ` Andrei Rybak
2018-07-26 15:57 ` Johannes Schindelin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.6.1807171204080.71@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=sbeller@google.com \
--cc=sunshine@sunshineco.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).