From: jgunthorpe@obsidianresearch.com (Jason Gunthorpe)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] MAINTAINERS: Add myself as co-maintainer to fpga mgr framework.
Date: Tue, 22 Nov 2016 09:35:56 -0700 [thread overview]
Message-ID: <20161122163556.GA3956@obsidianresearch.com> (raw)
In-Reply-To: <47eb36a7-ee48-53bd-fbdc-15225c3147ec@xilinx.com>
On Tue, Nov 22, 2016 at 08:48:57AM +0100, Michal Simek wrote:
> TBH. I think it is not a bad option. I do normally have backup person
> for all repos I do maintain. It doesn't mean that second maintainer does
> something but it has all accesses to repos you maintain.
I agree, it is a good idea to have a maintainer team model as early as
possible just because stuff does happen. We've had to recover from MIA
maintainers in RDMA and TPM, and it is not really nice. Generally
a lot of patches just get dropped :(
Jason
prev parent reply other threads:[~2016-11-22 16:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 21:49 [PATCH 1/2] MAINTAINERS: Update fpga-mgr entry with new linux-fpga mailing list Moritz Fischer
2016-11-21 21:49 ` [PATCH 2/2] MAINTAINERS: Add myself as co-maintainer to fpga mgr framework Moritz Fischer
2016-11-21 22:09 ` Marek Vasut
2016-11-22 2:29 ` atull
2016-11-22 7:48 ` Michal Simek
2016-11-22 8:07 ` Greg Kroah-Hartman
2016-11-22 8:28 ` Michal Simek
2016-11-22 16:35 ` Jason Gunthorpe [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=20161122163556.GA3956@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=linux-arm-kernel@lists.infradead.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).