Re: Our cumbersome mailing list workflow
- From
Philip Oakley <philipoakley@iee.org>
- Date
- Nov 28, 2014, 11:13 UTC
- Message-ID
- <A2A8D58134DA4E0B8D9CCE3D29E5319E@PhilipOakley>
- In-Reply-To
- <vpqoars7b8z.fsf@anie.imag.fr>
From: "Matthieu Moy" <Matthieu.Moy@grenoble-inp.fr>
Show 22 quoted lines
> Torsten Bögershausen <tboegi@web.de> writes: > >> On 2014-11-25 01.28, Michael Haggerty wrote: >> [] >>> Let me list the aspects of our mailing list workflow that I find >>> cumbersome as a contributor and reviewer: >>> >>> * Submitting patches to the mailing list is an ordeal of configuring >>> format-patch and send-email and getting everything just right, using >>> instructions that depend on the local environment. >> Typically everything fits into ~/.gitconfig, >> which can be carried around on a USB-Stick. > > I personnally submit all my Git patches from a machine whose > /usr/sbin/sendmail knows how to send emails, so for me configuration > is > super simple. But I can imagine the pain of someone working on various > machines with various network configuration and normally using a > webmail > to send emails. Sharing ~/.gitconfig does not always work because on > machine A you only can use one SMTP server, and on machine B only > another ...
The bit I find awkward for the send-email step is the creation of the "to" and "cc" lists. I tend to create the command line in a separate file so that I can re-use it for V2 etc. and even then I end up with all patches going to the full to/cc list.
Michael's original discussion email did feel to summarise the isses [1] well.
-- Philip [1] System Problems are Wicked problems : http://en.wikipedia.org/wiki/Wicked_problem www.poppendieck.com/wicked.htm