All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antonio Quartulli <antonio@meshcoding.com>
To: "André Gaul" <gaul@web-yard.de>
Cc: 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: Wed, 11 Jun 2014 08:04:21 +0200	[thread overview]
Message-ID: <5397F165.7060006@meshcoding.com> (raw)
In-Reply-To: <5397280D.5050608@web-yard.de>

[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]



On 10/06/14 17:45, André Gaul wrote:
> 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!) ;)

Honestly I don't know if there is any documentation.

Sending a patch to a mailing list is a way to ask for a
review/evaluation, which works well so I don't see a clear reason why it
should be changed (just that it appears archaic does not seem to be a
good reason).

Only maintainer having their tree on a trusted host can send pull
requests without attaching the patches (we do send pull requests along
with the patches exactly for this reason..).

And actually git also provides many comfortable commands to do that :)
so...! :)



Cheers,



-- 
Antonio Quartulli


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

  reply	other threads:[~2014-06-11  6:04 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 [this message]
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=5397F165.7060006@meshcoding.com \
    --to=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.