From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: proxy-maint@gentoo.org
Subject: Re: [gentoo-dev] scheme herd needs help
Date: Sat, 16 Feb 2013 15:40:48 +0100 [thread overview]
Message-ID: <1361025648.1920.58.camel@belkin4> (raw)
In-Reply-To: <20130203214225.GB18608@freyja.radhermit.com>
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
El dom, 03-02-2013 a las 13:42 -0800, Tim Harder escribió:
> On 2013-02-03 Sun 13:21, Cyprien Nicolas wrote:
> >> Who is behind lisp overlay? Only you or more people that could also be
> >> contacted to try to get them maintaining guile? Thanks for the info
> >
> >We are 2 or 3 non-dev volonteers. pchrist is busy with life and
> >common-lisp stuff, grozin and radhermit give a hand on some
> >packages. The lisp overlay guys are easily rechable through
> >#gentoo-lisp or gentoo-lisp mailing list.
> >
> >About guile, I'm the only one having touched it for the last 2 years
> >[1]. I think I could proxy-maint it, with an experienced dev in
> >eselect modules and multiple SLOT packages.
>
> I can help maintain guile and will proxy stuff for you (but I'm not in
> the proxy-maintainers herd).
>
> Tim
I think it's not a problem, you don't need to be in that herd for
proxying. What final list of packages will be proxy maintained finally
then? Looks like guile... but not sure about hop (most people would
prefer to get in tree version also fixed instead of needing to rely on
lisp overlay :/)
Thanks
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2013-02-16 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-02 12:54 [gentoo-dev] scheme herd needs help Pacho Ramos
2013-02-03 11:36 ` Cyprien Nicolas
2013-02-03 13:39 ` Pacho Ramos
2013-02-03 21:21 ` Cyprien Nicolas
2013-02-03 21:42 ` Tim Harder
2013-02-16 14:40 ` Pacho Ramos [this message]
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=1361025648.1920.58.camel@belkin4 \
--to=pacho@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=proxy-maint@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