From: "Marijn Schouten (hkBst)" <hkBst@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: gentoo-project@lists.gentoo.org
Subject: [gentoo-project] Re: [gentoo-dev] Re: About herds and their non-existant use
Date: Fri, 23 May 2008 07:18:16 +0200 [thread overview]
Message-ID: <48365398.7050206@gentoo.org> (raw)
In-Reply-To: <g132ek$knv$1@ger.gmane.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Tiziano � wrote:
| Marius Mauch wrote:
|>> - only have one location where members of a given team are listed,
|>> currently it's possible and quite likely that herds.xml and the mail
|>> alias files get out of sync
| Well, we need one location where the name of the team is mapped to the
| actual mail-alias. But I don't get what you're trying to say...
While we're changing things around, perhaps we can then also standardize the mail alias to
team@gentoo.org.
What Marius is saying though is that there are two files that handle people and their
herds. One XML for saying who is in a herd and one for each herd mail alias on woodpecker
with a list of developer email prefixes.
Marijn
- --
Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML
<http://www.gentoo.org/proj/en/lisp/>, #gentoo-{lisp,ml} on FreeNode
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkg2U5gACgkQp/VmCx0OL2wIVQCfVRE1/lP60+cspM6Zay5kyVwl
yUUAn1rBssAT2ndNpo55NLI3vzLrWdIN
=RMvL
-----END PGP SIGNATURE-----
--
gentoo-project@lists.gentoo.org mailing list
prev parent reply other threads:[~2008-05-23 7:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 21:42 [gentoo-project] About herds and their non-existant use Marius Mauch
2008-05-21 22:38 ` Marius Mauch
2008-05-21 23:16 ` Ferris McCormick
2008-05-21 23:36 ` Marius Mauch
[not found] ` <g132ek$knv$1@ger.gmane.org>
2008-05-23 5:18 ` Marijn Schouten (hkBst) [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=48365398.7050206@gentoo.org \
--to=hkbst@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gentoo-project@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