From: "André Gaul" <gaul@web-yard.de>
To: Marek Lindner <mareklindner@neomailbox.ch>,
b.a.t.m.a.n@lists.open-mesh.org
Cc: Antonio Quartulli <antonio@meshcoding.com>
Subject: Re: [B.A.T.M.A.N.] [PATCH] remove unnecessary logspam
Date: Sun, 15 Jun 2014 14:32:07 +0200 [thread overview]
Message-ID: <539D9247.6030001@web-yard.de> (raw)
In-Reply-To: <3526098.vVitn7FrQj@diderot>
Hi Marek,
Am 14.06.2014 03:44, schrieb Marek Lindner:
> 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) ?
I got used to simple webuis for reviews+comments à 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é
--
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
prev parent reply other threads:[~2014-06-15 12:32 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
2014-06-15 12:32 ` André Gaul [this message]
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=539D9247.6030001@web-yard.de \
--to=gaul@web-yard.de \
--cc=antonio@meshcoding.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=mareklindner@neomailbox.ch \
/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.