From: Marek Lindner <mareklindner@neomailbox.ch>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: "André Gaul" <gaul@web-yard.de>,
"Antonio Quartulli" <antonio@meshcoding.com>
Subject: Re: [B.A.T.M.A.N.] [PATCH] remove unnecessary logspam
Date: Sat, 14 Jun 2014 09:44:55 +0800 [thread overview]
Message-ID: <3526098.vVitn7FrQj@diderot> (raw)
In-Reply-To: <5397280D.5050608@web-yard.de>
[-- Attachment #1: Type: text/plain, Size: 642 bytes --]
On Tuesday 10 June 2014 17:45:17 André 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 & comment
patches by everyone.
What is the alternative you have in mind (no vendor lock-in please) ?
Cheers,
Marek
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-06-14 1:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 19:53 [B.A.T.M.A.N.] [PATCH] remove unnecessary logspam André Gaul
2014-06-09 8:54 ` Antonio Quartulli
2014-06-09 17:14 ` André Gaul
2014-06-09 21:05 ` Antonio Quartulli
2014-06-09 21:36 ` André Gaul
2014-06-10 6:01 ` Antonio Quartulli
2014-06-10 15:38 ` André Gaul
2014-06-10 15:40 ` Antonio Quartulli
2014-06-10 15:45 ` André Gaul
2014-06-11 6:04 ` Antonio Quartulli
2014-06-14 1:44 ` Marek Lindner [this message]
2014-06-15 12:32 ` André Gaul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3526098.vVitn7FrQj@diderot \
--to=mareklindner@neomailbox.ch \
--cc=antonio@meshcoding.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=gaul@web-yard.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.