Gnus development mailing list
 help / color / mirror / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: ding@gnus.org
Subject: Re: Posting Git patch series with Gnus
Date: Fri, 29 Nov 2019 10:56:00 +0100	[thread overview]
Message-ID: <m28snzf1lb.fsf@gmail.com> (raw)
In-Reply-To: <87r21s8fe3.fsf@mid.deneb.enyo.de>

>>>>> On Thu, 28 Nov 2019 11:27:32 +0100, Florian Weimer <fw@deneb.enyo.de> said:

    Florian> Are there any ready-made Lisp macros to post a branch as a patch
    Florian> series, allowing me to edit the cover letter before actual sending?

    Florian> Gnus' MIME handling seems to be more reliable than that of git
    Florian> send-email, and I'd like to use the Gnus setup and not the slightly
    Florian> more problematic /usr/sbin/sendmail configuration for sending mail.
    Florian> Another benefit is archival of outgoing email in Gnus.

    Florian> Any suggestions?

This doesnʼt help with the MIME portion [1], but you can create an nndraft
group called eg 'patches' with 'G m', then do

git format-patch --numbered-files -o ~/News/drafts/patches --cover-letter HEAD~4

Which would create files 0 1 2 3 4, with '0' containing the cover
letter. Unfortunately '0' is not a valid article number, so you'd have
to script shifting all the numbers up by one. You'd probably want a
'--add-header=Gcc:<something>' to get the gnus archiving to work.

Since itʼs an nndraft group, you can do 'e' on any individual message
to edit it, and then use 'D S' to send all messages (or mark
individual messages with '#' and do 'D s').

Robert

Footnotes:
[1]  What's wrong with git send-email's mime handling?




      parent reply	other threads:[~2019-11-29  9:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-28 10:27 Florian Weimer
2019-11-28 12:53 ` Lars Ingebrigtsen
2019-11-29  9:56 ` Robert Pluim [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m28snzf1lb.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=ding@gnus.org \
    --cc=fw@deneb.enyo.de \
    /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.
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 NNTP newsgroup(s).