| 1 |
On Wed, Apr 23, 2003 at 08:43:41AM +0100, Mark Gordon wrote: |
| 2 |
> On Tue, 22 Apr 2003 15:36:55 -0700 |
| 3 |
> Robin H.Johnson <robbat2@g.o> wrote: |
| 4 |
> |
| 5 |
[snip] |
| 6 |
> |
| 7 |
> Also, I would think that if you are submitting an ebuild for a new |
| 8 |
> package including a summary of what it is and why it is useful (keep it |
| 9 |
> short) since then a developer is more likely on seeing it to say, "Wow, |
| 10 |
> I want that," and get it in to the tree. |
| 11 |
> |
| 12 |
> If an update to an existing ebuild for a new package version fixes a |
| 13 |
> major problem, mention that briefly rather than just submitting it to |
| 14 |
> bugzilla as a version bump. |
| 15 |
|
| 16 |
Yes, this is probably the most helpful way for me to determine which |
| 17 |
ebuilds I want to touch when I look at the bug-wranglers list. Because I |
| 18 |
don't want to get stuck with the bugs later for something I don't use or |
| 19 |
don't have an interest in, I go through and pick up ebuilds that have a |
| 20 |
description that interests me. I'm sure other developers do the same. |
| 21 |
Additionally, it helps the bug-wranglers people decide where to assign |
| 22 |
those bugs. |
| 23 |
|
| 24 |
[snip] |
| 25 |
|
| 26 |
-- |
| 27 |
Jon Portnoy |
| 28 |
avenj/irc.freenode.net |
| 29 |
|
| 30 |
-- |
| 31 |
gentoo-dev@g.o mailing list |
Archives