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 5, 2016, 08:24 UTC

Message-ID

<alpine.DEB.2.20.1608051023560.5786@virtualbox>

In-Reply-To

<20160804201751.GA9592@starla>

Hi Eric,

On Thu, 4 Aug 2016, Eric Wong wrote:

> Stefan Beller <sbeller@google.com> wrote:
> > On Thu, Aug 4, 2016 at 8:58 AM, Johannes Schindelin
> > <Johannes.Schindelin@gmx.de> wrote:
> > > I guess I have no really good idea yet, either, how to retain the ease of
> > > access of sending mails to the list, yet somehow keep a strong tie with
> > > the original data stored in Git.
> > 
> > Does it have to be email? Transmitting text could be solved
> > differently as well.
> 
> I've thought a lot about this over the years still think email
> is the least bad.

> Anti-spam tools for other messaging systems are far behind,
> proprietary, or non-existent.  bugzilla.kernel.org has been hit
> hard lately and I see plenty of bug-tracker-to-mail spam as a
> result from projects that use web-based bug trackers.

> I guess a blockchain (*coin) implementation might work (like
> hashcash is used for email anti-spam), but the ones I've glanced
> at all look like a bigger waste of electricity than email
> filters.

> Of course, centralized systems are unacceptable to me;
> and with that I'll never claim any network service I run
> will be reliable :)