From: "Diego Elio Pettenò" <flameeyes@flameeyes.eu>
To: gentoo-dev@lists.gentoo.org
Subject: Proxy maintainers in metadata.xml (was Re: [gentoo-dev] introduce a soft-limit policy for changing other developers ebuilds)
Date: Tue, 04 Dec 2012 09:06:29 -0800 [thread overview]
Message-ID: <50BE2D95.1000201@flameeyes.eu> (raw)
In-Reply-To: <50BE1E3E.9070406@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 679 bytes --]
On 04/12/2012 08:01, Rick "Zero_Chaos" Farina wrote:
> I feel the description field is already overloaded when there is a proxy
> situation, maybe it would be best to define a field for this. Also
> english isn't primary language for everyone in the world so if the
> policy could actually be specific on this it would benefit everyone.
Or maybe we can just agree that common sense rules all, and we always
set the proxied maintainer as assignee, and the proxy maintainer as CC..
because, you know, that's the only way a proxy maintainer can
close/change a bug at all.
--
Diego Elio Pettenò — Flameeyes
flameeyes@flameeyes.eu — http://blog.flameeyes.eu/
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 553 bytes --]
next prev parent reply other threads:[~2012-12-04 17:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-02 15:21 [gentoo-dev] introduce a soft-limit policy for changing other developers ebuilds hasufell
2012-12-02 15:38 ` Rich Freeman
2012-12-02 19:30 ` Markos Chandras
2012-12-04 1:18 ` Ben de Groot
2012-12-04 7:43 ` Ian Whyman
2012-12-04 9:19 ` Markos Chandras
2012-12-04 15:42 ` Alec Warner
2012-12-04 18:54 ` Markos Chandras
2012-12-06 10:53 ` Ben de Groot
2012-12-04 8:10 ` Rick "Zero_Chaos" Farina
2012-12-04 9:23 ` Markos Chandras
2012-12-04 16:01 ` Rick "Zero_Chaos" Farina
2012-12-04 17:06 ` Diego Elio Pettenò [this message]
2012-12-04 17:28 ` Proxy maintainers in metadata.xml (was Re: [gentoo-dev] introduce a soft-limit policy for changing other developers ebuilds) Rick "Zero_Chaos" Farina
2012-12-04 18:35 ` Sergey Popov
2012-12-04 18:48 ` Diego Elio Pettenò
2012-12-04 18:51 ` Markos Chandras
2012-12-06 11:02 ` Ben de Groot
2012-12-06 13:28 ` Markos Chandras
2012-12-06 15:27 ` Peter Stuge
2012-12-06 15:54 ` Ian Stakenvicius
2012-12-06 16:04 ` Peter Stuge
2012-12-06 19:07 ` Markos Chandras
2012-12-08 17:48 ` Jeroen Roovers
2012-12-04 17:01 ` [gentoo-dev] introduce a soft-limit policy for changing other developers ebuilds hasufell
2012-12-04 17:17 ` Rick "Zero_Chaos" Farina
2012-12-04 17:32 ` hasufell
2012-12-04 17:46 ` Rick "Zero_Chaos" Farina
2012-12-04 18:17 ` hasufell
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=50BE2D95.1000201@flameeyes.eu \
--to=flameeyes@flameeyes.eu \
--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