public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-dev-announce] Packages up for grabs --  xmerlin, yoswink, chtekk, omp, tantive, mueli, bluebird, hncaldwell, caleb
Date: Thu, 17 Jun 2010 20:29:01 +0300	[thread overview]
Message-ID: <AANLkTin6uEbHZ_WmIfokpqrnNW6QtgnpAqOhQGlTsADE@mail.gmail.com> (raw)
In-Reply-To: <20100608195911.GA20808@muiri>

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

2010/6/8 José María <nimiux@gentoo.org>

> On Tue, Jun 08, 2010 at 06:25:17PM +0200, Jeroen Roovers wrote:
> > On Tue, 8 Jun 2010 13:14:07 +0200
> > José María Alonso <nimiux@gentoo.org> wrote:
> >
> > > I would be very pleased to maintain this package:
> > >
> > > > app-doc/repodoc
> >
> > > Is there any chance I can maintain this package?. What do
> > > I have to do?.
> >
> > You could provide unified patches to the ebuilds to fix the four
> > outstanding bugs[1] with the package. Someone should CC themselves on
> > those bugs who has commit access for the thing to work, of course.
> > Maybe the live (-9999) ebuild could use some work too.
> >
> >
> > Regards,
> >      jer
> >
> >
> > [1] https://bugs.gentoo.org/buglist.cgi?quicksearch=repodoc
> >
>
> Thank you very much for pointing me in the right direction.
> I'll begin to work in those bugs.
>
> Cheers.
>
> Ok, then I won't mask this package for removal ( I was about to do it right
now when I accidentally remembered this thread ) for now. If the bugs are
still unresolved after 30 days I will have to mask it for removal. In the
meantime, if you have working patches for the repodoc bugs [1], I can commit
them for you and proxy this package for you until you gain tree access

[1]: http://bugs.gentoo.org/buglist.cgi?quicksearch=repodoc

[-- Attachment #2: Type: text/html, Size: 2076 bytes --]

  parent reply	other threads:[~2010-06-17 17:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100602071850.GA25028@veller.net>
2010-06-02 11:02 ` [gentoo-dev] Re: [gentoo-dev-announce] Packages up for grabs -- xmerlin, yoswink, chtekk, omp, tantive, mueli, bluebird, hncaldwell, caleb Dirkjan Ochtman
2010-06-02 11:32 ` Patrick Lauer
     [not found] ` <AANLkTileo4SvrwefXyqDblcpG9El0rrkm1V2zFKzfi3z@mail.gmail.com>
2010-06-02 15:34   ` Diego E. “Flameeyes” Pettenò
2010-06-02 17:59 ` Hans de Graaff
2010-06-03 18:16 ` Tobias Scherbaum
2010-06-08 11:14 ` José María Alonso
2010-06-08 16:25   ` Jeroen Roovers
2010-06-08 19:59     ` José María Alonso
2010-06-09 19:40       ` Victor Ostorga
2010-06-11 19:12         ` Ben de Groot
2010-06-11 19:26           ` Ben de Groot
2010-06-11 20:53             ` Maciej Mrozowski
2010-06-11 21:50             ` Ben de Groot
2010-06-12  9:28               ` Markos Chandras
2010-06-12 12:09               ` Alex Alexander
2010-06-13 13:36                 ` Markos Chandras
2010-06-11 19:26           ` Kacper Kowalik
2010-06-17 17:29       ` Markos Chandras [this message]
2010-06-18 16:42         ` José María Alonso
2010-06-18 22:26           ` Markos Chandras

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=AANLkTin6uEbHZ_WmIfokpqrnNW6QtgnpAqOhQGlTsADE@mail.gmail.com \
    --to=hwoarang@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