From: Thilo Bangert <bangert@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] irregular metdata.xml check
Date: Sun, 27 May 2007 14:17:53 +0200 [thread overview]
Message-ID: <200705271417.56549.bangert@gentoo.org> (raw)
In-Reply-To: <20070523211933.GJ17511@curie-int.orbis-terrarum.net>
[-- Attachment #1: Type: text/plain, Size: 1709 bytes --]
"Robin H. Johnson" <robbat2@gentoo.org> said:
> On Wed, May 23, 2007 at 07:49:43PM +0200, Thilo Bangert wrote:
> > Also, many ebuilds put the herds email address as an additional
> > <maintainer>. This is simply redundant and unless complaints are
> > raised, all herd <maintainer> tags will be removed and replaced by
> > the appropriate <herd> tag instead. Work on this will start over the
> > weekend.
>
> No.
>
> See the thread about automatic assignment for more about this.
> More importantly, once the automatic stuff goes into play, the
> existence of the herd tag will only matter on metadata that does not
> have any other maintainer.
sorry - to have missed this earlier.
from your proposal:
>Case 2 - Metadata contains a single maintainer
>----------------------------------------------
> The herd field is not used.
so, you want to ignore the herd tag, as soon as there is a single
maintainer tag? why?
we have <herd> on every single package in the tree (well ~1900 packages
with <herd>no-herd</herd>). my guess is that most of the roughly 4500
packages that currently have a <herd> and a <maintainer> which is not a
<herd>, will need to adjust their metadata to reflect the situation where
the maintainer should get the bug asssigned and the herd gets CC'd...
IMHO the herd should always get an email on bugs with packages belonging
to the herd... if this is not the case, what is the purpose of the herd?
or asked differently: what can the herd in <maintainer> give you that the
<herd> can't?
other than that i (still) agree with the overall proposal. lets just make
sure to codify the policy which has been agreed upon...
regards
Thilo
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-05-27 12:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 17:49 [gentoo-dev] irregular metdata.xml check Thilo Bangert
2007-05-23 18:24 ` Chris Gianelloni
2007-05-23 18:34 ` [gentoo-dev] " Markus Ullmann
2007-05-23 19:01 ` [gentoo-dev] " Timothy Redaelli
2007-05-23 21:19 ` Robin H. Johnson
2007-05-27 12:17 ` Thilo Bangert [this message]
2007-05-27 14:30 ` Radoslaw Stachowiak
2007-06-10 20:58 ` [gentoo-dev] " Ryan Hill
2007-06-10 22:20 ` Robin H. Johnson
-- strict thread matches above, loose matches on Subject: below --
2007-06-10 23:41 [gentoo-dev] " Thilo Bangert
2007-06-11 5:55 ` Rémi Cardona
2007-06-11 8:20 ` Marijn Schouten (hkBst)
2007-06-11 8:26 ` Petteri Räty
2007-06-11 9:07 ` Robin H. Johnson
2007-06-11 16:34 ` Harald van Dijk
2009-12-07 11:56 Thilo Bangert
2009-12-07 12:13 ` Ulrich Mueller
2009-12-07 13:20 ` Thilo Bangert
2009-12-07 17:04 ` Hans de Graaff
2009-12-07 20:20 ` Thilo Bangert
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=200705271417.56549.bangert@gentoo.org \
--to=bangert@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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