public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jon Portnoy <avenj@gentoo.org>
To: Ragnar Hojland Espinosa <ragnar@linalco.com>
Cc: Peter Ruskin <aoyu93@dsl.pipex.com>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Ebuilds not getting in :(
Date: Tue, 22 Apr 2003 10:05:52 -0400	[thread overview]
Message-ID: <20030422140551.GA10278@cerberus.oppresses.us> (raw)
In-Reply-To: <20030422135007.GA23742@linalco.com>

On Tue, Apr 22, 2003 at 03:50:07PM +0200, Ragnar Hojland Espinosa wrote:
> On Tue, Apr 22, 2003 at 02:17:46PM +0100, Peter Ruskin wrote:
> > I couldn't agree more!
> > 
> > Perhaps cx86 for contributors' ebuilds?
> 
> That sounds like a good idea.  contributor / community ebuilds.   We can
> wait and see if we can get some input from official devs on the situation
> and then determine our course of action.
> 
> > My ebuilds (#13452 and #14205) were submitted in January.
> 
> My last ones are already obsoleted by another stable release ;)
> 
> -- 
> Ragnar Hojland - Project Manager
> Linalco "Especialistas Linux y en Software Libre"
> http://www.linalco.com Tel: +34-91-5970074 Fax: +34-91-5970083
> 
> --
> gentoo-dev@gentoo.org mailing list

The problem is that in order to make intelligent commit decisions, you 
need to understand the ebuild and (likely) the program.

There are some proposals being discussed internally to help deal with 
the ebuild update situation. Let's see where those take us before we try 
other approaches.

-- 
Jon Portnoy
avenj/irc.freenode.net

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-04-22 14:05 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 [this message]
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
     [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=20030422140551.GA10278@cerberus.oppresses.us \
    --to=avenj@gentoo.org \
    --cc=aoyu93@dsl.pipex.com \
    --cc=gentoo-dev@gentoo.org \
    --cc=ragnar@linalco.com \
    /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