From: NeilBrown <neilb@suse.de>
To: Aapo Laine <aapo.laine@shiftmail.org>
Cc: "Kristleifur Daðason" <kristleifur@gmail.com>,
linux-raid <linux-raid@vger.kernel.org>
Subject: Re: potentially lost largeish raid5 array..
Date: Wed, 5 Oct 2011 13:13:16 +1100 [thread overview]
Message-ID: <20111005131316.27314c0b@notabene.brown> (raw)
In-Reply-To: <4E8898C4.8060803@shiftmail.org>
[-- Attachment #1: Type: text/plain, Size: 2093 bytes --]
On Sun, 02 Oct 2011 19:00:52 +0200 Aapo Laine <aapo.laine@shiftmail.org>
wrote:
> On 10/02/11 01:21, Aapo Laine wrote:
> > Actually we could even open a new mailing list or maybe there is
> > something better in web 2.0, like a wiki, for these MD code
> > explanations. Explanations in a wiki can be longer, there can be user
> > discussions, and such lines of comments do not need to be pushed as
> > far as Linus.
>
> Sorry, I wrote this before reading other replies. Kristleifur already
> proposed what might be optimal, that is, GitHub
Anyone who wants to is welcome to create a kernel tree on github, apply
patches, and send me pull requests. To just email me patches.
However the patches arrive I will need to review them at least until I have
enough experience with the person to have good reason to trust their patches.
Typically the extent of review will drop as a history of good patches grows
until I just pull any that looks vaguely credible.
I don't think we need any new infrastructure to allow this. We just need
people with an interest to create and submit patches.
If someone says "I've created some patches but they aren't getting into
mainline because ...." of some reason, maybe because I keep ignoring them or
losing them in mail inbox or something, then it might be time to look at
technology solutions to make it easier for new contributors to get patches
in. But until those new contributors are trying there isn't much point
making it easier for them.
Thanks,
NeilBrown
>
> > I think concentrating all code explanation requests, discussions,
> > and/or at least the answers, onto something like a wiki could prevent
> > double-questions. Unfortunately I know nothing about wikis or other
> > web 2.0 technologies. Maybe someone in this ML can suggest a solution?
>
> Ditto
>
> +1 on the github
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2011-10-05 2:13 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 1:50 potentially lost largeish raid5 array Thomas Fjellstrom
2011-09-23 4:32 ` NeilBrown
2011-09-23 4:49 ` Thomas Fjellstrom
2011-09-23 4:58 ` Roman Mamedov
2011-09-23 5:10 ` Thomas Fjellstrom
2011-09-23 7:06 ` David Brown
2011-09-23 7:37 ` Thomas Fjellstrom
2011-09-23 12:56 ` Stan Hoeppner
2011-09-23 13:28 ` David Brown
2011-09-23 16:22 ` Thomas Fjellstrom
2011-09-23 23:24 ` Stan Hoeppner
2011-09-24 0:11 ` Thomas Fjellstrom
2011-09-24 12:17 ` Stan Hoeppner
2011-09-24 13:11 ` (unknown) Tomáš Dulík
2011-09-24 15:16 ` potentially lost largeish raid5 array David Brown
2011-09-24 16:38 ` Stan Hoeppner
2011-09-25 13:03 ` David Brown
2011-09-25 14:39 ` Stan Hoeppner
2011-09-25 15:18 ` David Brown
2011-09-25 23:58 ` Stan Hoeppner
2011-09-26 10:51 ` David Brown
2011-09-26 19:52 ` Stan Hoeppner
2011-09-26 20:29 ` David Brown
2011-09-26 23:28 ` Krzysztof Adamski
2011-09-27 3:53 ` Stan Hoeppner
2011-09-24 17:48 ` Thomas Fjellstrom
2011-09-24 5:59 ` Mikael Abrahamsson
2011-09-24 17:53 ` Thomas Fjellstrom
2011-09-25 18:07 ` Robert L Mathews
2011-09-26 6:08 ` Mikael Abrahamsson
2011-09-26 2:26 ` Krzysztof Adamski
2011-09-23 5:11 ` NeilBrown
2011-09-23 5:22 ` Thomas Fjellstrom
2011-09-23 8:09 ` Thomas Fjellstrom
2011-09-23 9:15 ` NeilBrown
2011-09-23 16:26 ` Thomas Fjellstrom
2011-09-25 9:37 ` NeilBrown
2011-09-24 21:57 ` Aapo Laine
2011-09-25 9:18 ` Kristleifur Daðason
2011-09-25 10:10 ` NeilBrown
2011-10-01 23:21 ` Aapo Laine
2011-10-02 17:00 ` Aapo Laine
2011-10-05 2:13 ` NeilBrown [this message]
2011-10-05 2:06 ` NeilBrown
2011-11-05 12:17 ` Alexander Lyakas
2011-11-06 21:58 ` NeilBrown
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=20111005131316.27314c0b@notabene.brown \
--to=neilb@suse.de \
--cc=aapo.laine@shiftmail.org \
--cc=kristleifur@gmail.com \
--cc=linux-raid@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).