From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:46130)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <alex.bennee@linaro.org>) id 1XgwV0-0001Yi-5I
	for qemu-devel@nongnu.org; Wed, 22 Oct 2014 10:02:55 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <alex.bennee@linaro.org>) id 1XgwUu-0004VE-Lp
	for qemu-devel@nongnu.org; Wed, 22 Oct 2014 10:02:50 -0400
Received: from static.88-198-71-155.clients.your-server.de
	([88.198.71.155]:43433 helo=socrates.bennee.com)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <alex.bennee@linaro.org>) id 1XgwUu-0004UT-G9
	for qemu-devel@nongnu.org; Wed, 22 Oct 2014 10:02:44 -0400
References: <87mw8rumhb.fsf@blackfin.pond.sub.org>
From: Alex =?utf-8?Q?Benn=C3=A9e?= <alex.bennee@linaro.org>
In-reply-to: <87mw8rumhb.fsf@blackfin.pond.sub.org>
Date: Wed, 22 Oct 2014 15:02:40 +0100
Message-ID: <8761fcgq2n.fsf@linaro.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Subject: Re: [Qemu-devel] MAINTAINERS leaves too many files uncovered
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>


Markus Armbruster <armbru@redhat.com> writes:

> In my experience, too many files are not covered by MAINTAINERS.
> scripts/get_maintainer.pl falls back to git then, unless you say
> --no-git-fallback.  Copies sent there tends to annoy their recipients
> without accomplishing all that much.
>
> Two obvious improvements:
>
> * Easy: Flip scripts/get_maintainer.pl's default to --no-git-fallback.
>   I'll post the obvious patch, please raise your objections there.

As it happens I do that in my .git/config, but...

> * Harder: improve MAINTAINERS coverage.

Well one problem is no MAINTAINER == no obvious tree to take you
patches. This is my main bugbear. I have a few patch series that touch a
smattering of files (e.g. logging improvements) that don't fall under
one particular sub-system but are probably a little too broad for the
trivial tree.

> Where are the unmaintained files?  Top-scoring directories outside
> tests/ and include/, files in subdirs not counted:
>
>     #files   directory
>     84  68%  .

I suspect there is a bunch of general infrastructure bits that has this
sort of property. Maybe some effort be made to move related bits into
sub-directories (with MAINTAINERS) where they are less likely to fall
in-between the cracks?

<snip>

> Ideas?  Takers?

My 0.2c ;-)

-- 
Alex Bennée