From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Soliciting input for a non-maintainer update (NMU) GLEP
Date: Sat, 22 Jun 2013 12:11:13 +0200 [thread overview]
Message-ID: <1371895873.30388.10.camel@localhost> (raw)
In-Reply-To: <robbat2-20130621T235922-795874263Z@orbis-terrarum.net>
El sáb, 22-06-2013 a las 00:06 +0000, Robin H. Johnson escribió:
[...]
> I'm not going into review systems here at all, I'm simply trying to have
> a policy of what changes are welcomed/blocked WITHOUT interaction from
> the listed maintainer(s) of a given package/herd.
[...]
In my case I would like to be always notified a change has been
committed (even forwarding gentoo-commits message to me), that will help
me to keep track of the committed changes, and learn more if they
corrected a bug caused by me ;)
Regarding what other can commit or not... I think a general good policy
would be to:
1. If package is not hardly broken -> report a bug to maintainer with a
1 week timeout. If he/she doesn't reply, go ahead.
2. If package is nonfunctional -> go ahead and fix it as soon as
possible!
next prev parent reply other threads:[~2013-06-22 10:11 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 18:50 [gentoo-dev] Soliciting input for a non-maintainer update (NMU) GLEP Robin H. Johnson
2013-06-21 19:04 ` Alexis Ballier
2013-06-21 19:07 ` Robin H. Johnson
2013-06-21 19:31 ` Alexis Ballier
2013-06-22 1:11 ` Tom Wijsman
2013-06-21 20:31 ` Michael Weber
2013-06-21 20:41 ` Michael Weber
2013-06-22 1:21 ` Tom Wijsman
2013-06-21 23:40 ` Mike Frysinger
2013-06-22 0:06 ` Robin H. Johnson
2013-06-22 0:17 ` Mike Frysinger
2013-06-22 0:26 ` Robin H. Johnson
2013-06-22 1:06 ` Mike Frysinger
2013-06-22 1:42 ` Robin H. Johnson
2013-06-22 3:28 ` Rick "Zero_Chaos" Farina
2013-06-22 9:00 ` Ulrich Mueller
2013-06-22 9:05 ` hasufell
2013-06-22 9:38 ` [gentoo-dev] Herds (was: Soliciting input for a non-maintainer update (NMU) GLEP) Ulrich Mueller
2013-06-22 9:48 ` [gentoo-dev] Herds hasufell
2013-06-22 9:46 ` [gentoo-dev] Soliciting input for a non-maintainer update (NMU) GLEP Ulrich Mueller
2013-06-22 10:43 ` Rich Freeman
2013-06-22 9:01 ` hasufell
2013-06-22 10:20 ` Michael Weber
2013-06-22 10:39 ` Rich Freeman
2013-06-22 10:52 ` Tom Wijsman
2013-06-22 17:59 ` Mike Frysinger
2013-06-22 9:16 ` Markos Chandras
2013-06-22 10:19 ` Tom Wijsman
2013-06-22 13:42 ` [gentoo-dev] " Michael Palimaka
2013-06-22 15:13 ` [gentoo-dev] " hasufell
2013-06-22 16:56 ` Robin H. Johnson
2013-06-22 10:11 ` Pacho Ramos [this message]
2013-06-23 3:01 ` Rick "Zero_Chaos" Farina
2013-06-27 18:18 ` hasufell
2013-06-27 19:29 ` Rick "Zero_Chaos" Farina
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=1371895873.30388.10.camel@localhost \
--to=pacho@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