From: Maurice van der Pot <griffon26@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Something to remember when using the new maintainer-* aliases
Date: Wed, 29 Jun 2005 21:55:09 +0200 [thread overview]
Message-ID: <20050629195509.GM19598@kfk4ever.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
Hi people,
I've already noticed a few people assigning to the new aliases, but
forgetting to put appropriate herds on the CC. This was mentioned in the
previous thread, but not everybody may have read that one.
So please keep in mind:
If a bug is submitted for a package of interest to a certain herd,
regardless whether the package is new or already in the tree and
without maintainer, it is usually best to put the herd on the CC.
That way if someone steps up to maintain the package and comments,
the herd is immediately notified. Also if the herd itself wants to take
a new package under its wing, it can reassign the bug.
Thanks,
Maurice.
--
Maurice van der Pot
Gentoo Linux Developer griffon26@gentoo.org http://www.gentoo.org
Creator of BiteMe! griffon26@kfk4ever.com http://www.kfk4ever.com
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2005-06-29 19:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050629195509.GM19598@kfk4ever.com \
--to=griffon26@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