On Wed, 2 May 2018, speck for Thomas Gleixner wrote:
> On Tue, 1 May 2018, speck for Kees Cook wrote:
> 
> > On Sun, Apr 15, 2018 at 05:25:09PM +0200, speck for Thomas Gleixner wrote:
> > > I've looked into patch series sending as well and I think I have an idea. I
> > > could provide a special speck-patchbomb@.... address where you could send
> > > quilt mbox file to. The remailer could simply extract the mbox from the
> > > crypted mail and remail the mails in the mbox as seperate mails. If you
> > > think that's useful, please let me know. It's trivial to implement as I
> > > have mbox handling code around already.
> > 
> > Did this address get set up? If not, what's the current workflow for
> > sending patches? Konrad's steps seemed to be missing some details (and
> > I don't use quilt).
> 
> Did not come around yet to set that up. I'll think about it later today

Here is at least a simple workaround for now:

# mkdir mail
# mkdir speck
# git format-patch -o mail -n --to speck@linutronix.de --thread --cover-letter v4.17-rc3..
# emacs mail/0000-cover-letter.patch
# speckify-gitmail -s "TEST" mail/ speck/
Now send the mails from speck/ in the way you would send from mail/

speckify-gitmail does the following for every file in mail/

 - Put a copy of the original From and Subject into the mail body

 - Sets the subject to '$PATCHPREFIX $NEWSUBJECT $N'

   e.g. [PATCH 0/3] TEST 0

 - Strip Cc's from the mail headers

 - Encrypt the mail body with the list key

 - Store the encrypted mail in speck/

It does not work with the following git format-patch options:
   --inline
   --attach

Script attached. Try -h if you need a reminder how it works

Thanks,

	tglx