Re: patch submission process, was Re: [PATCH v6 06/16] merge_recursive: abort properly upon errors

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Aug 6, 2016, 08:44 UTC
Message-ID: <alpine.DEB.2.20.1608061038460.5786@virtualbox>
In-Reply-To: <20160805184656.GA463@starla>

Hi Eric,

On Fri, 5 Aug 2016, Eric Wong wrote:

Show 16 quoted lines

> Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > On Thu, 4 Aug 2016, Stefan Beller wrote:
> > > git send-email/format-patch recently learned to include a base commit
> > 
> > You may have noticed that my mail-patch-series.sh-generated code
> > submissions contain that base commit. But they still do not contain the
> > SHA-1s of my local commits corresponding to the patches, and even if they
> > did, the replies with suggested edits would most likely have lost said
> > information.
> > 
> > I also hate to break it to you that git-send-email is not going to be part
> > of any solution.
> 
> I think it ought to be.  Some reasons I like emailing patches are:
> 
> [...]

What I said is that *git-send-email* is not going to be part of any solution.

Note that I said *git-send-email*, not "emailing patches".

What many people on this list forget is that few email users *ever* touch their email configuration. Asking them to figure out their SMTP settings and then to make git-send-email work is, uhm, quite a bit unrealistic.

Ciao, Dscho