Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-scm
Navigation:
Lists: gentoo-scm: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-scm@g.o
From: Mike Auty <ikelos@g.o>
Subject: Re: Status report, 2009/04/10
Date: Sat, 11 Apr 2009 22:30:14 +0100
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hiya Robin,

Great work on the pushing on with all this, thanks very much, it's
greatly appreciated!  5:)  It's excellent you managed to get some of the
git guys in on the thread and offering such useful patches, it looks
like things are getting better and better for having the gentoo repo
working great in git.

I was wondering how your Thin Manifest stuff was getting on?  I figured
since you're doing all this, I'd offer my meagre python skills for
anything that might need coding up for that (I've always meant to start
tinkering with portage anyway, just never quite got round to it).  So
please let me know if you've any documentation or anything that needs
looking over, or any basic tools that need putting in place, and I'll
see what I can do (time and skill permitting obviously)...  5:)

Mike  5:)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)

iEYEARECAAYFAknhC+YACgkQu7rWomwgFXrfFACfRK2IyAkWG7y4HaK19XgiHW7u
R6EAniktd1XYCsmu2cG6+weqOFi7HZBs
=y5ux
-----END PGP SIGNATURE-----


Replies:
Re: Status report, 2009/04/10
-- Robin H. Johnson
References:
Status report, 2009/04/10
-- Robin H. Johnson
Navigation:
Lists: gentoo-scm: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Status report, 2009/04/10
Next by thread:
Re: Status report, 2009/04/10
Previous by date:
Re: Splitting gentoo-x86 repository for easier consumption
Next by date:
Re: Status report, 2009/04/10


Updated Jun 17, 2009

Summary: Archive of the gentoo-scm mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.