Re: [PATCH 0/1] Improve automatic setup of tracking for new branches

From: Philippe Blain <levraiphilippeblain@gmail.com>
To: Ben Boeckel <mathstuf@gmail.com>
Cc: git@vger.kernel.org, "Martin Ågren" <martin.agren@gmail.com>,
	"Junio C Hamano" <gitster@pobox.com>, "Jeff King" <peff@peff.net>,
	"Jeff Hostetler" <jeffhost@microsoft.com>,
	"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
	"Taylor Blau" <me@ttaylorr.com>
Subject: Re: [PATCH 0/1] Improve automatic setup of tracking for new branches
Date: Fri, 30 Jul 2021 12:01:36 -0400	[thread overview]
Message-ID: <7b50ebc6-7b28-412d-b124-9bd54750c922@gmail.com> (raw)
In-Reply-To: <YQQFWtKo8b1WJIGe@erythro.dev.benboeckel.internal>

Hi again,

Le 2021-07-30 à 09:57, Ben Boeckel a écrit :
> On Fri, Jul 30, 2021 at 09:35:39 -0400, Philippe Blain wrote:
>> Le 2021-07-28 à 22:01, Ben Boeckel a écrit :
>>
>> Small nit: usually when sending a second version of a patch, you would use
>> the '-v2' argument to 'git format-patch' so that the patch and cover letter
>> is prefixed [PATCH v2].
> 
> Yes, I realized that I had forgotten the `--reroll-count=` argument when
> making this patch (I suppose a way to store the Cc list for a topic
> somewhere would be nice so I didn't lean so heavily on shell history
> would help this).

There is 'format.cc', but it's not branch-specific, so you would have to
use one worktree per branch with extension.worktreeConfig...

> 
> FWIW, my main gripe with the email-based workflow is the lack of
> coordinated metadata (LWN has numerous comments by me about my views if
> you're curious, but I should really formalize them into blog posts). But
> when in Rome :) .
> 

I agree. I almost always use Gitgitgadget [1], which keeps track of the CC list for
me, of updating the re-roll count, of adding the in-reply-to header such that subsequent
versions of the series are sent as a response to the cover letter of the previous version,
generating a range-diff against the previous version,
commenting on the PR when the series is mentioned in "What's cooking", etc.

Some things it does not support are: sending a patch as a response to some random
mail on the list, which is sometimes useful, reading the commit notes to generate
in-patch commentaries [2], customizing the diff generated by 'format-patch'.
Other things are listed at [3].

Recently I've even been using only the terminal with Gitgitgadget:
I use 'git branch --edit-description'
to write my cover letter, and then use the 'gh' GitHub CLI to open my PR:

$ git config --get-regexp alias.desc*
alias.desc-title !git config branch.$(git branch --show-current).description | head -1
alias.desc-body !git config branch.$(git branch --show-current).description | tail -n+3
$ gh pr create --title "$(git desc-title)" --body "$(git desc-body)" --head phil-blain:$(git branch --show-current)

Cheers,
Philippe.

[1] https://gitgitgadget.github.io/
[2] https://github.com/gitgitgadget/gitgitgadget/issues/173
[3] https://github.com/gitgitgadget/gitgitgadget/issues