From: Arthur Britto <ahbritto@iat.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] submiting ebuilds
Date: 10 May 2003 19:20:19 -0700 [thread overview]
Message-ID: <1052619619.7345.5.camel@credit> (raw)
In-Reply-To: <200305101911.13933.george@gentoo.org>
On Sat, 2003-05-10 at 19:11, George Shapovalov wrote:
> http://www.gentoo.org/doc/en/ebuild-submit.xml
> In short - create a new bug on bugs.gentoo.org. But please see the link for
> detailed instructions, such as, which category should the bug belong, etc.
That's nice, but I've been tracking an ebuild submission (bug #8997)
since October.
How many months should someone expect to babysit an ebuild till it is
placed in portage as unstable? 6 months?
-Arthur
--
Copyright (c) 2003 Arthur Britto, All Rights Reserved, Redistribution of this message requires written permission.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-05-11 2:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-11 1:54 [gentoo-dev] submiting ebuilds Amiel Martin
2003-05-11 2:11 ` George Shapovalov
2003-05-11 2:20 ` Arthur Britto [this message]
2003-05-11 3:44 ` Caleb Shay
2003-05-11 9:27 ` Sven Vermeulen
2003-05-11 2:24 ` Amiel Martin
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=1052619619.7345.5.camel@credit \
--to=ahbritto@iat.com \
--cc=gentoo-dev@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