From: Jon Portnoy <avenj@gentoo.org>
To: Mark Gordon <mark.gt@flash-gordon.me.uk>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Ebuilds not getting in :(
Date: Wed, 23 Apr 2003 08:46:28 -0400 [thread overview]
Message-ID: <20030423124628.GA27832@cerberus.oppresses.us> (raw)
In-Reply-To: <20030423084341.2caa31f4.mark.gt@flash-gordon.me.uk>
On Wed, Apr 23, 2003 at 08:43:41AM +0100, Mark Gordon wrote:
> On Tue, 22 Apr 2003 15:36:55 -0700
> Robin H.Johnson <robbat2@gentoo.org> wrote:
>
[snip]
>
> Also, I would think that if you are submitting an ebuild for a new
> package including a summary of what it is and why it is useful (keep it
> short) since then a developer is more likely on seeing it to say, "Wow,
> I want that," and get it in to the tree.
>
> If an update to an existing ebuild for a new package version fixes a
> major problem, mention that briefly rather than just submitting it to
> bugzilla as a version bump.
Yes, this is probably the most helpful way for me to determine which
ebuilds I want to touch when I look at the bug-wranglers list. Because I
don't want to get stuck with the bugs later for something I don't use or
don't have an interest in, I go through and pick up ebuilds that have a
description that interests me. I'm sure other developers do the same.
Additionally, it helps the bug-wranglers people decide where to assign
those bugs.
[snip]
--
Jon Portnoy
avenj/irc.freenode.net
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-04-23 12:46 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 7:38 [gentoo-dev] Ebuilds not getting in :( Klavs Klavsen
2003-04-22 12:59 ` Frantz Dhin
2003-04-22 13:09 ` Ragnar Hojland Espinosa
2003-04-22 13:17 ` Peter Ruskin
2003-04-22 13:24 ` FRLinux
2003-04-22 13:30 ` Klavs Klavsen
2003-04-22 13:50 ` Ragnar Hojland Espinosa
2003-04-22 14:05 ` Jon Portnoy
2003-04-22 16:18 ` Brad Laue
2003-04-23 15:25 ` Peter Ruskin
2003-04-23 18:18 ` Paul de Vrieze
2003-04-22 14:26 ` Dan Armak
2003-04-22 14:57 ` Peter Ruskin
2003-04-22 15:40 ` Tony Clark
2003-04-22 15:45 ` Ragnar Hojland Espinosa
2003-04-22 16:00 ` Klavs Klavsen
2003-04-22 16:14 ` Tony Clark
2003-04-22 16:23 ` William Hubbs
2003-04-22 16:59 ` Jon Portnoy
2003-04-22 17:55 ` Mark Bainter
2003-04-22 18:00 ` Klavs Klavsen
2003-04-22 18:06 ` Jon Portnoy
2003-04-25 16:58 ` Brad Laue
2003-04-25 17:31 ` foser
2003-04-25 21:03 ` Brad Laue
2003-04-26 0:38 ` foser
2003-04-22 19:11 ` Fredrik Jagenheim
2003-04-22 23:53 ` Fernand Albarracin
2003-04-22 15:57 ` Brian Jackson
2003-04-22 22:07 ` Brian Jackson
2003-04-22 22:36 ` Robin H.Johnson
2003-04-23 7:43 ` Mark Gordon
2003-04-23 12:46 ` Jon Portnoy [this message]
[not found] ` <20030425134659.I30851@leftmind.net>
2003-04-25 21:59 ` Robin H.Johnson
2003-04-23 2:56 ` Brian Jackson
2003-04-23 15:27 ` Peter Fein
2003-04-23 15:38 ` Grant Goodyear
2003-04-24 18:20 ` Brian Jackson
2003-04-23 5:47 ` Thomas Arnhold
-- strict thread matches above, loose matches on Subject: below --
2003-04-24 0:32 Stroller
2003-04-24 3:50 ` George Shapovalov
2003-04-25 1:01 Stroller
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=20030423124628.GA27832@cerberus.oppresses.us \
--to=avenj@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=mark.gt@flash-gordon.me.uk \
/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