From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [RFC] missing <herd> tag in metadata.xml
Date: Fri, 11 May 2007 14:57:32 -0600 [thread overview]
Message-ID: <f22lbt$5un$1@sea.gmane.org> (raw)
In-Reply-To: <200705110305.26339.bangert@gentoo.org>
Thilo Bangert wrote:
> open questions:
>
> - what does it mean when the package is maintained by a herd and an
> additional maintainer? how does one determine the order in which to
> contact multiple maintainers?
See "Planning for automatic assignment of bugs"
(http://thread.gmane.org/gmane.linux.gentoo.devel/48485)
--
where to now? if i had to guess
dirtyepic gentoo org i'm afraid to say antarctica's next
9B81 6C9F E791 83BB 3AB3 5B2D E625 A073 8379 37E8 (0x837937E8)
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-05-11 21:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 15:38 [gentoo-dev] [RFC] missing <herd> tag in metadata.xml Thilo Bangert
2007-05-10 15:45 ` Mike Doty
2007-05-10 17:38 ` Thilo Bangert
2007-05-10 20:11 ` Bo Ørsted Andresen
2007-05-11 1:05 ` Thilo Bangert
2007-05-11 20:57 ` Ryan Hill [this message]
2007-05-12 14:26 ` Thilo Bangert
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='f22lbt$5un$1@sea.gmane.org' \
--to=dirtyepic@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