Re: [PATCH 1/6] man.7: srcfix

[Alejandro Colomar <alx@kernel.org>]

[-- Attachment #1.1: Type: text/plain, Size: 1695 bytes --]

Hi Branden,

On 2023-07-29 11:11, G. Branden Robinson wrote:
> Hi Alex,
> 
> At 2023-07-28T22:56:10+0200, Alejandro Colomar wrote:
>> On 2023-07-28 19:57, G. Branden Robinson wrote:
>>> Clean up in preparation for "MR sed".
>>
>> Moved this into the commit message.
> 
> Thanks!
> 
> [...]
>> I wonder why all this appears in your email body.  How did you
>> generate it?  I bet not with git-format-patch(1), or that you modified
>> it manually?
> 
> The latter.  It had been so long since I had submitted a series of
> patches to this list that I forgot that I had a shell script to help me
> with it.  I used it for v2 of the two remaining patches, so if those
> are well-formed, all I have to do in the future is remember my script.

I wonder why you need a script.  I usually do the following:

$ git format-patch -o patches/ master..HEAD --cover-letter -v1 \
	--cc linux-man@vger.kernel.org --to mtk.manpages@gmail.com;
$ vi ./patches/v1-0000*;  # edit the cover letter
$ git send-email ./patches/v1-*;

which has grown finger memory so much that a script would
over-complicate it.

(I have a global gitignore for ./patches/; see:)

$ sed -n '/^\[core]/,/^$/p' .gitconfig
[core]
	editor = vim
	excludesFile = ~/.config/git/gitignore

$ cat .config/git/gitignore 
# vim(1) tmp files
*.swp
*.swo

# Store patches here:
/patches/


And BTW, for -v2 and subsequent revisions, --range-diff is very
interesting in git-format-patch(1).  Other times, though, it's very
confusing, and --interdiff is more appropriate.


Cheers,
Alex


-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]