public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fredrik Jagenheim <humming@pobox.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Ebuilds not getting in :(
Date: Tue, 22 Apr 2003 21:11:00 +0200	[thread overview]
Message-ID: <20030422191100.GA10102@pobox.com> (raw)
In-Reply-To: <1051016369.4102.46.camel@entropy>

On Tue, Apr 22, 2003 at 02:59:30PM +0200, Frantz Dhin wrote:
> A distribution that prides itself by being flexible and bleeding edge
> should also have smooth and flexible policies. For insight into where
> bureaucratic policies brings a distribution refer to Debian.

While I understand the frustration in not getting feedback on work
put down, there's always PORTDIR_OVERLAY. If someone, apart from you,
have a need for the latest, greatest version of the package they can
always download the ebuild from bugs.gentoo.org and put it locally.

I guess some enterprising person with some time on their hands always
can do a hack which will keep your PORTDIR_OVERLAY synced to
bugs.gentoo.org.

Anyways, I don't think the problem stems from ebuilds not being
commited to CVS fast enough, but the complete lack of feedback from
developers what happens to bugs/ebuilds/fixes that is entered to
bugs.gentoo.org. I know developers are busy, but a simple acknowledge
from the assigned developer of the status would help calm down the
commiters. As of now, many times all what happens to the bug-entry is
that you see it gets assigned and then silence...

I have personally spent a couple of evenings tracking down long
standing bugs and belived that I have reached some sort of solution on
them. But since I haven't heard any feedback I'm not sure if someone
cares, my fixes were so wrong they didn't even deserve a mention or
there is a better fix...

Yeah, I know. I spent the first half of this letter telling you that
your problem was non-existant, and then spending the other half
ranting on my problems as if they were the end of the world. Have
mercy on me, I've had a rough day. ;)

//H

-- 
To segfault is human; to bluescreen moronic. 

--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-04-22 19:11 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 [this message]
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
     [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=20030422191100.GA10102@pobox.com \
    --to=humming@pobox.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