public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Klavs Klavsen <kl@vsen.dk>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Ebuilds not getting in :(
Date: 22 Apr 2003 18:00:09 +0200	[thread overview]
Message-ID: <1051027209.2986.81.camel@amd.vsen.dk> (raw)
In-Reply-To: <200304221557.42803.aoyu93@dsl.pipex.com>

[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]

On Tue, 2003-04-22 at 16:57, Peter Ruskin wrote:
> On Tuesday 22 Apr 2003 15:26, Dan Armak wrote:
> >  The second will facilitate quick acceptance of user-submitted ebuilds
> > in some way - probably drawing upon the submitters in one way or
> > another.
> 
> I'm more than willing to maintain ebuilds I submit.
> 

Same here. What are the requirements for being a maintainer?
I don't think one has to make the newest version available ASAP.
This f.ex. didn't happen with drip - which was why I created a new
version myself.

I think people who submit ebuilds should automacally be added as
maintainer of the ebuild. If they contribute with a newer version of a
given ebuild - then they should be added as maintainer - keeping the old
maintainer too. 

It's a Community distro and I don't think anyone will mind - as long as
it's all build on volutarity - ie. make a newer version if you like -
don't if you don't.
-- 
Regards,
Klavs Klavsen, GSEC - kl@vsen.dk - http://www.vsen.dk

Working with Unix is like wrestling a worthy opponent. 
Working with windows is like attacking a small whining child 
who is carrying a .38.				

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-04-22 16:00 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 [this message]
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=1051027209.2986.81.camel@amd.vsen.dk \
    --to=kl@vsen.dk \
    --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