From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gaul@web-yard.de>
Message-ID: <539D9247.6030001@web-yard.de>
Date: Sun, 15 Jun 2014 14:32:07 +0200
From: =?ISO-8859-1?Q?Andr=E9_Gaul?= <gaul@web-yard.de>
MIME-Version: 1.0
References: <53957653.5000406@meshcoding.com>
 <539726E7.9070500@meshcoding.com> <5397280D.5050608@web-yard.de>
 <3526098.vVitn7FrQj@diderot>
In-Reply-To: <3526098.vVitn7FrQj@diderot>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [B.A.T.M.A.N.] [PATCH] remove unnecessary logspam
Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking
 <b.a.t.m.a.n@lists.open-mesh.org>
List-Id: The list for a Better Approach To Mobile Ad-hoc Networking
 <b.a.t.m.a.n.lists.open-mesh.org>
List-Unsubscribe: <https://lists.open-mesh.org/mm/options/b.a.t.m.a.n>,
 <mailto:b.a.t.m.a.n-request@lists.open-mesh.org?subject=unsubscribe>
List-Archive: <http://lists.open-mesh.org/pipermail/b.a.t.m.a.n/>
List-Post: <mailto:b.a.t.m.a.n@lists.open-mesh.org>
List-Help: <mailto:b.a.t.m.a.n-request@lists.open-mesh.org?subject=help>
List-Subscribe: <https://lists.open-mesh.org/mm/listinfo/b.a.t.m.a.n>,
 <mailto:b.a.t.m.a.n-request@lists.open-mesh.org?subject=subscribe>
To: Marek Lindner <mareklindner@neomailbox.ch>, b.a.t.m.a.n@lists.open-mesh.org
Cc: Antonio Quartulli <antonio@meshcoding.com>

Hi Marek,

Am 14.06.2014 03:44, schrieb Marek Lindner:
> Traditionally, patches on the mailing list make it easy to review & comme=
nt=20
> patches by everyone.
>=20
> What is the alternative you have in mind (no vendor lock-in please) ?

I got used to simple webuis for reviews+comments =E0 la github or
bitbucket. I can fully understand that kernel developers do not want to
depend on a company such as github. The only free software alternative
that comes to my mind is gitlab but I don't have any experience with
gitlab and big projects.

Patches on the mailing list make it easy for people who already do so
for some time. E.g., if you're not on the list, then it's not that easy
to apply a submitted patch (you'll have to copy+paste the patch). Also
the context of a patch is missing in the mail: you don't see the full
patched version and every potential reviewer has to apply the patch
her/himself, thus collectively wasting time for a task that can be fully
automated. Furthermore, we've just seen in this thread how vulnerable
the procedure is to misbehaving mail clients. ;) This also wasted some
of my and Antonio's time.

As said before: I just wanted to know about the reasons -- refusing
vendor lock-ins certainly is a reason and I can agree on trading a bit
of comfort for independence. :)

Cheers and keep up the good work on B.A.T.M.A.N.,
Andr=E9

--=20
Homepage   http://page.math.tu-berlin.de/~gaul
github     https://github.com/andrenarchy
Twitter    https://twitter.com/#!/andrenarchy
Diaspora   https://diasp.org/u/andrenarchy
           (you won't find me on facebook!)
Jabber     gaul@web-yard.de
PGP Key    0x0FA9170E