[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20161122163556.GA3956@obsidianresearch.com>
Date: Tue, 22 Nov 2016 09:35:56 -0700
From: Jason Gunthorpe <jgunthorpe@...idianresearch.com>
To: Michal Simek <michal.simek@...inx.com>
Cc: atull <atull@...nsource.altera.com>,
Moritz Fischer <moritz.fischer@...us.com>,
linux-kernel@...r.kernel.org, marex@...x.de, mbrugger@...e.com,
mike.looijmans@...ic.nl, linux-arm-kernel@...ts.infradead.org,
Moritz Fischer <mdf@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-fpga@...r.kernel.org
Subject: Re: [PATCH 2/2] MAINTAINERS: Add myself as co-maintainer to fpga mgr
framework.
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
Powered by blists - more mailing lists