From: George Shapovalov <george@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Herds, Teams and Projects
Date: Sat, 29 Apr 2006 00:47:11 +0200 [thread overview]
Message-ID: <200604290047.12079.george@gentoo.org> (raw)
In-Reply-To: <20060429002853.0be12db2@c1358217.kevquinn.com>
Saturday, 29. April 2006 00:28, Kevin F. Quinn (Gentoo) Ви написали:
> On Fri, 28 Apr 2006 21:29:58 +0200
>
> George Shapovalov <george@gentoo.org> wrote:
> > Friday, 28. April 2006 21:20, Kevin F. Quinn (Gentoo) wrote:
> > > 3) A herd does not have an email address - it's not a person or
> > > group of people so an email address is nonsensical.
> >
> > 3a) A herd has an associated alias
> > 3b) Individual developers add yourself (explicitly or get added by
> > means of herds.xml (gentoo module in cvs, under misc)) to this alias.
>
> I thought this was the whole point of seemant's original message - it
> is projects or teams that have a mail alias. Some herds happen to have
> the same name as a project or team, but it's the team that you email,
> not the herd. It doesn't make sense to email a herd, any more than it
> makes sense to send email to an ebuild. It does however make sense to
> email the maintainer of a herd, in the same way as it makes sense to
> email the maintainer of an ebuild.
Well, yes, you don't email a herd per se (if we strictly stick to these
terms :)), but rather maintainers associated with it (via some project or
listed in herds.xml). Above is just a mechanism that makes sure your email
gets delivered to the right people. But we really now just do nitpicking of
the terminology (which, although, the original message by Seemant was about).
I just wanted to mention aliases to clarify the connection between packages,
maintainers and herds.xml/metadata.xml.
George
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-04-28 22:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 0:29 [gentoo-dev] Herds, Teams and Projects Seemant Kulleen
2006-04-27 0:52 ` Mark Loeser
2006-04-27 1:38 ` Seemant Kulleen
2006-04-27 1:58 ` Daniel Goller
2006-04-27 2:38 ` Donnie Berkholz
2006-04-27 3:58 ` Mike Frysinger
2006-04-27 4:11 ` Donnie Berkholz
2006-04-27 7:22 ` Kevin F. Quinn (Gentoo)
2006-04-27 7:46 ` Alin Nastac
2006-04-27 14:27 ` Chris Gianelloni
2006-04-27 17:54 ` Kevin F. Quinn (Gentoo)
2006-04-27 19:00 ` Chris Gianelloni
2006-04-27 17:11 ` Paul de Vrieze
2006-04-27 17:55 ` Henrik Brix Andersen
2006-04-28 9:11 ` Paul de Vrieze
2006-04-28 19:20 ` Kevin F. Quinn (Gentoo)
2006-04-28 19:29 ` George Shapovalov
2006-04-28 22:28 ` Kevin F. Quinn (Gentoo)
2006-04-28 22:47 ` George Shapovalov [this message]
2006-05-01 20:01 ` Paul de Vrieze
2006-04-27 14:54 ` Stuart Herbert
2006-04-27 18:14 ` Mike Frysinger
2006-04-27 18:59 ` Stuart Herbert
2006-04-27 19:31 ` Chris Gianelloni
2006-04-27 18:33 ` Chris Gianelloni
2006-04-29 3:42 ` Mike Frysinger
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=200604290047.12079.george@gentoo.org \
--to=george@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