public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ROX: maintainer-wanted and apps out of date
Date: Mon, 12 Sep 2005 13:51:01 -0400	[thread overview]
Message-ID: <1126547461.455.45.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <1126544414.10585.33.camel@localhost>

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

On Mon, 2005-09-12 at 13:00 -0400, Peter Hyman wrote:
> What I WOULD like to know is:
> 
> 1) what IS the status of svyatogor and lanius?

<CIA-1> svyatogor * gentoo/xml/htdocs/doc/ru/handbook/ (5 files): 
<CIA-1> handbook indices for x86, AMD64, and SPARC archs. Bug #101063.
Commit is done

This is from today.  At least svyatogor is active.

> 2) Who is maintaining ROX and what's going to be done about it.

Since svyatogor is active, I would say that he is maintaining it.  My
"usual" answer to the "when will this be added to the tree" question is
"when it is done".

Your ebuilds were not ready for inclusion, which means that the
maintainer doesn't just need time to drop your ebuilds into an overlay,
emerge them, and commit them, but instead has to take time to resolve
any issues with them.  Sometimes this is as simple as changing a word or
adding some quotes.  Sometimes this can be rather extensive.  Having a
100% correct ebuild, as we have been *trying* to tell you, reduces the
work on the maintainer to almost nil.  A partially correct ebuild can
possibly even increase the amount of work needed, if the ebuild is in
especially bad shape.  I understand your frustration, just understand
that a partially-correct ebuild could possibly not be any more helpful
than stating "a new version of $foo is out" when it comes to developer
time.  Ciaran is only trying to help you write a better ebuild, so that
next time you make one, it will be correct and can go into the tree
without editing.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

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

  parent reply	other threads:[~2005-09-12 17:55 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-11 13:58 [gentoo-dev] ROX: maintainer-wanted and apps out of date Peter Hyman
2005-09-11 15:50 ` Maurice van der Pot
2005-09-11 16:42   ` Peter Hyman
2005-09-11 19:24     ` Maurice van der Pot
2005-09-11 21:02     ` Alin Nastac
2005-09-12  0:10       ` Aron Griffis
2005-09-12  7:04         ` Alin Nastac
2005-09-12  0:14       ` Peter Hyman
2005-09-12  0:25         ` Ciaran McCreesh
2005-09-12  0:38           ` Alec Warner
2005-09-12 11:55           ` Carsten Lohrke
2005-09-12 14:03             ` Chris Gianelloni
2005-09-12 14:26               ` Re[2]: " Jakub Moc
2005-09-12 14:28               ` Maurice van der Pot
2005-09-12 15:41                 ` Peter Hyman
2005-09-12 16:12                   ` Martin Schlemmer
2005-09-12 17:00                     ` Peter Hyman
2005-09-12 17:12                       ` Jan Kundrát
2005-09-12 17:25                       ` Stephen P. Becker
2005-09-12 17:51                       ` Chris Gianelloni [this message]
2005-09-12 17:03             ` Ciaran McCreesh
2005-09-12 17:32               ` Carsten Lohrke
2005-09-12 17:40                 ` Ciaran McCreesh
2005-09-12 17:56                 ` Re[2]: " Jakub Moc
2005-09-12 18:53                   ` Carsten Lohrke
2005-09-12 19:21                     ` Ciaran McCreesh
2005-09-13  0:20                       ` Nathan L. Adams
2005-09-12 19:26                     ` [gentoo-dev] " Dan Meltzer
2005-09-12  0:27         ` [gentoo-dev] " Stephen P. Becker
2005-09-12  0:36           ` Peter Hyman

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=1126547461.455.45.camel@cgianelloni.nuvox.net \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-dev@lists.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