From: "Williams, Dan J" <dan.j.williams@intel.com>
To: NeilBrown <neilb@suse.de>
Cc: stan@hardwarefreak.com, lists@yazzy.org, linux-raid@vger.kernel.org
Subject: Re: Recovery of failed RAID 6 and LVM
Date: Thu, 29 Sep 2011 17:18:45 -0700 [thread overview]
Message-ID: <CABE8wwt_3DjPqFg5Gm064Gi5OMFFYjuQ9ToAjS+-TYOX+M2ZCw@mail.gmail.com> (raw)
In-Reply-To: <20110930090720.57534d81@notabene.brown>
On Thu, Sep 29, 2011 at 4:07 PM, NeilBrown <neilb@suse.de> wrote:
>> What if as a starting point we could get a Patchwork queue hosted
>> somewhere so you could at least start formally delegating incoming
>> patches for an apprentice to disposition?
>
> I don't know much about Patchwork ... what sort of value does it add?
It just makes things more transparent. It allows a submitter to have
a web interface to view the state of a patch: accepted, rejected,
under review. Allows a maintainer or a group of maintainers to see
the backlog and assign (delegate) patches between them. It also
automates the collection of Acked-by, Reviewed-by, etc tags.
> But I don't think much of the idea of delegation. I don't see a thriving
> developer community full of people who want work delegated to them.
So I only meant "delegate" in the Patchwork parlance to make "who is
merging this md/mdadm patch" clear as the apprentice ramps up. But
this is probably too much mechanics.
It simply sounds like you want a similar situation like what happened
with git. I.e. a "Junio" to take over but you'll still be around to
course correct and send patches.
--
Dan
--
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
next prev parent reply other threads:[~2011-09-30 0:18 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-25 7:55 Recovery of failed RAID 6 and LVM Marcin M. Jessa
2011-09-25 8:39 ` Stan Hoeppner
2011-09-25 10:07 ` Marcin M. Jessa
2011-09-25 13:15 ` Phil Turmel
2011-09-25 14:16 ` Marcin M. Jessa
2011-09-25 16:43 ` Phil Turmel
2011-09-25 14:41 ` Marcin M. Jessa
2011-09-25 16:19 ` Phil Turmel
2011-09-25 21:40 ` NeilBrown
2011-09-25 21:58 ` Marcin M. Jessa
2011-09-25 22:18 ` NeilBrown
2011-09-25 22:21 ` Marcin M. Jessa
[not found] ` <4E804062.3020700@yazzy.org>
2011-09-26 9:31 ` NeilBrown
2011-09-26 10:53 ` Marcin M. Jessa
2011-09-26 11:10 ` NeilBrown
2011-09-27 19:12 ` Marcin M. Jessa
2011-09-27 23:13 ` NeilBrown
2011-09-28 2:50 ` Stan Hoeppner
2011-09-28 7:10 ` Marcin M. Jessa
2011-09-28 7:51 ` David Brown
2011-09-28 16:12 ` Stan Hoeppner
2011-09-28 16:30 ` Marcin M. Jessa
2011-09-28 18:56 ` Thomas Fjellstrom
2011-09-28 19:26 ` Marcin M. Jessa
2011-09-28 19:42 ` Thomas Fjellstrom
2011-09-28 23:49 ` NeilBrown
2011-09-29 9:03 ` David Brown
2011-09-29 15:21 ` Stan Hoeppner
2011-09-29 17:14 ` David Brown
2011-09-29 18:28 ` Dan Williams
2011-09-29 23:07 ` NeilBrown
2011-09-30 0:18 ` Williams, Dan J [this message]
2011-10-05 2:15 ` NeilBrown
2011-09-28 10:38 ` Michal Soltys
2011-09-28 13:20 ` Brad Campbell
2011-09-28 19:02 ` Thomas Fjellstrom
2011-09-28 16:31 ` Stan Hoeppner
2011-09-28 16:37 ` Marcin M. Jessa
2011-09-28 19:03 ` Thomas Fjellstrom
2011-09-28 19:29 ` Marcin M. Jessa
2011-09-28 19:43 ` Thomas Fjellstrom
2011-09-30 20:01 ` Marcin M. Jessa
2011-09-30 21:47 ` Thomas Fjellstrom
2011-09-30 22:30 ` Marcin M. Jessa
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=CABE8wwt_3DjPqFg5Gm064Gi5OMFFYjuQ9ToAjS+-TYOX+M2ZCw@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=lists@yazzy.org \
--cc=neilb@suse.de \
--cc=stan@hardwarefreak.com \
/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).