public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: "André Gaul" <gaul@web-yard.de>
To: Antonio Quartulli <antonio@meshcoding.com>,
	The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] [PATCH] remove unnecessary logspam
Date: Tue, 10 Jun 2014 17:45:17 +0200	[thread overview]
Message-ID: <5397280D.5050608@web-yard.de> (raw)
In-Reply-To: <539726E7.9070500@meshcoding.com>

Am 10.06.2014 17:40, schrieb Antonio Quartulli:
> Oh you are right. I should have continued using mutt...

hehe, I'm glad it works now! :) I'll resubmit in a minute as a new thread.

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!) ;)

Cheers,
André

-- 
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

  reply	other threads:[~2014-06-10 15:45 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 [this message]
2014-06-11  6:04                 ` Antonio Quartulli
2014-06-14  1:44                 ` Marek Lindner
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=5397280D.5050608@web-yard.de \
    --to=gaul@web-yard.de \
    --cc=antonio@meshcoding.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox