On Thu, 2006-05-04 at 18:09 -0500, Daniel Goller wrote:
> -BEGIN PGP SIGNED MESSAGE-
> ./dev-perl/Event-ExecFlow (dvd::rip dep)
> ./dev-perl/AnyEvent(dvd::rip dep)
Perl herd will grab these. For that matter, the metadata already points
to us...
~mcummings
signature.asc
Descripti
On Monday 08 May 2006 00:47, Denis Dupeyron wrote:
> Does the media-video herd^H^H^H^Hgroup automatically inherit this one ? If
> not, and if nobody volunteers, I'm willing to salvage it. I have somewhere
> an ebuild for kino-0.8.1 that includes an --as-needed fix.
Feel free to join media-video tea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Denis Dupeyron wrote:
> On 5/5/06, Daniel Goller <[EMAIL PROTECTED]> wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> The following packages require a new maintainer, some might just be
>> absorbed into their herds w/o a direct maintain
On 5/5/06, Daniel Goller <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> The following packages require a new maintainer, some might just be
> absorbed into their herds w/o a direct maintainer leaving them to the
> teams maintaining those herds, others might face
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexandre Buisse wrote:
> On Fri, May 5, 2006 at 10:02:10 +0200, Daniel Goller wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> The following packages require a new maintainer, some might just be
>> absorbed into their herds w/o a d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tuan Van wrote:
> Daniel Goller wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> The following packages require a new maintainer, some might just be
>> absorbed into their herds w/o a direct maintainer leaving them to the
>> teams maint
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Mylchreest wrote:
> On Thu, May 04, 2006 at 06:09:39PM -0500, Daniel Goller <[EMAIL PROTECTED]>
> wrote:
>
> Assuming there are no objections I can take over the following.
>
>> ./app-benchmarks/cpuburn
>> ./app-benchmarks/bonnie++
>
> Regards
Daniel Goller wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The following packages require a new maintainer, some might just be
absorbed into their herds w/o a direct maintainer leaving them to the
teams maintaining those herds, others might face extinction w/o a direct
maintainer.
./net
On Thursday 04 May 2006 19:09, Daniel Goller wrote:
> ./games-emulation/mupen64-riceplugin
> ./games-emulation/mupen64-glide64
> ./games-emulation/mupen64-glN64
> ./games-emulation/mupen64-blight-tr64gl
> ./games-emulation/mupen64-blight-input
> ./games-emulation/mupen64-jttl_sound
> ./games-emulat
On Fri, May 5, 2006 at 10:02:10 +0200, Daniel Goller wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> The following packages require a new maintainer, some might just be
> absorbed into their herds w/o a direct maintainer leaving them to the
> teams maintaining those herds, others mi
On Thu, May 04, 2006 at 06:09:39PM -0500, Daniel Goller <[EMAIL PROTECTED]>
wrote:
Assuming there are no objections I can take over the following.
> ./app-benchmarks/cpuburn
> ./app-benchmarks/bonnie++
Regards,
John
--
Role:Gentoo Linux Kernel Lead
Gentoo Linux:http://www.gent
Thanks thats what I was looking for.
On Fri, May 05, 2006 at 08:42:31AM +0200, Kevin F. Quinn (Gentoo) wrote:
> On Thu, 4 May 2006 21:20:48 -0500
> spradlim <[EMAIL PROTECTED]> wrote:
>
> > I have a question that I havn't been able to find that is somewhat
> > related to the following email. I k
On Thu, 4 May 2006 21:20:48 -0500
spradlim <[EMAIL PROTECTED]> wrote:
> I have a question that I havn't been able to find that is somewhat
> related to the following email. I know and understand Linux very
> well. I also know how ebuilds work. So how do I go about maintaining
> packages and gett
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
spradlim wrote:
> I have a question that I havn't been able to find that is somewhat
> related to the following email. I know and understand Linux very well.
> I also know how ebuilds work. So how do I go about maintaining packages
> and getting them
I have a question that I havn't been able to find that is somewhat
related to the following email. I know and understand Linux very well.
I also know how ebuilds work. So how do I go about maintaining packages
and getting them into portage. For example I would like to maintain a
munin, munin-plu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The following packages require a new maintainer, some might just be
absorbed into their herds w/o a direct maintainer leaving them to the
teams maintaining those herds, others might face extinction w/o a direct
maintainer.
./app-admin/gtkdiskfree
./sc
16 matches
Mail list logo