From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mareklindner@neomailbox.ch>
From: Marek Lindner <mareklindner@neomailbox.ch>
Date: Sat, 14 Jun 2014 09:44:55 +0800
Message-ID: <3526098.vVitn7FrQj@diderot>
In-Reply-To: <5397280D.5050608@web-yard.de>
References: <53957653.5000406@meshcoding.com>
 <539726E7.9070500@meshcoding.com> <5397280D.5050608@web-yard.de>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart8252938.vKBAQ0E4YQ";
 micalg="pgp-sha1"; protocol="application/pgp-signature"
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: b.a.t.m.a.n@lists.open-mesh.org
Cc: =?ISO-8859-1?Q?Andr=E9?= Gaul <gaul@web-yard.de>, Antonio Quartulli <antonio@meshcoding.com>


--nextPart8252938.vKBAQ0E4YQ
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"

On Tuesday 10 June 2014 17:45:17 Andr=E9 Gaul wrote:
> btw: do you have any pointers to documentation that can help me
> understand why the kernel developers still use email as the primary
> channel for submitting patches? Given the fact that git gracefully
> handles the transmission of code, the handling of all code via email
> appears archaic and too complicated to me. (no flame war intended, I
> just want to learn about the reasons!) ;)

Traditionally, patches on the mailing list make it easy to review & com=
ment=20
patches by everyone.

What is the alternative you have in mind (no vendor lock-in please) ?

Cheers,
Marek

--nextPart8252938.vKBAQ0E4YQ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAABAgAGBQJTm6kXAAoJEFNVTo/uthzA8VsH/3Qp4aNr/1uGR5wgilfiwsoc
husyfnHjeNQZaaRUBBYlexvk5g2q/6t2JjbHFzA5SKEMAbm9yj528PvJW8Vqx1WJ
QrOAFXd+HbllmHG5keRMZbS+L27dlenkQPIEuK0nNQVoMeHdsz8eXTk4blyAmv/Z
OaNwW419/b3EK0A7zWUXzoMMhro5PmXd4kQHndICauOz+5i8RzUFlcmbr193NzdC
DyFf3Yw46qUAcTGn/McZf63q3QqR0euyfdUWBc93fqK6nZHxJhdU6HXjeIaifqPT
qBstKN961OOnojsQWpaMNBylBI3U1fqm80GyEZwXJJ2xz9mARSmFV7ej+MxkPQI=
=Jys+
-----END PGP SIGNATURE-----

--nextPart8252938.vKBAQ0E4YQ--