From: Peter Volkov <pva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Two herds (and four extra?)
Date: Thu, 22 Jul 2010 13:04:45 +0400 [thread overview]
Message-ID: <1279789485.6915.64.camel@tablet> (raw)
In-Reply-To: <20100721133422.32e4b8ae@epia.jer-c2.orkz.net>
В Срд, 21/07/2010 в 13:34 +0200, Jeroen Roovers пишет:
> This is madness, people. Two herds and four separately mentioned
> developers? Why don't you join a herd? Go on, it's fun and you don't
> have to be alone!
Jeroen, sometimes I add myself as maintainer at the same time being part
of herd for two reasons: 1. this makes clear that package has dedicated
maintainer, 2. mail client filters bug mail that are assigned on me and
on herd giving herd less priority. I really hope that semi-automatic bug
assignment will help to avoid problem b-w have now...
--
Peter.
prev parent reply other threads:[~2010-07-22 9:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 11:34 [gentoo-dev] Two herds (and four extra?) Jeroen Roovers
2010-07-21 12:36 ` Tony "Chainsaw" Vroon
2010-07-21 12:58 ` Jeroen Roovers
2010-07-21 14:44 ` Anthony G. Basile
2010-07-21 16:11 ` Jeroen Roovers
2010-07-22 10:09 ` Chip Parker
2010-07-22 12:13 ` Anthony G. Basile
2010-07-22 17:19 ` Jeroen Roovers
2010-07-22 9:04 ` Peter Volkov [this message]
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=1279789485.6915.64.camel@tablet \
--to=pva@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