From: Brian Harring <ferringb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Clarification of packages cd's for 2005.1
Date: Fri, 16 Sep 2005 15:31:05 -0500 [thread overview]
Message-ID: <20050916203105.GB17982@nightcrawler> (raw)
In-Reply-To: <1080.60.234.144.216.1126902227.squirrel@www.rout.co.nz>
[-- Attachment #1: Type: text/plain, Size: 479 bytes --]
On Sat, Sep 17, 2005 at 08:23:47AM +1200, Nick Rout wrote:
> Thanks for the clarification Chris.
>
> On a semi-related matter I was looking for the catalyst .spec files, and
> see a thread pointing at cvs, however I believe that as a non-dev mortal I
> can't get access to gentoo cvs. Is that so? If it is then how does one get
> the spec files? The old catalyst howto seems to have disappeared too.
http://www.gentoo.org/cgi-bin/viewcvs.cgi
Is a start ;)
~harring
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-09-16 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 2:51 [gentoo-dev] Clarification of packages cd's for 2005.1 Nick Rout
2005-09-16 12:54 ` Chris Gianelloni
2005-09-16 20:23 ` Nick Rout
2005-09-16 20:31 ` Brian Harring [this message]
2005-09-16 20:47 ` Lars Weiler
2005-09-16 21:20 ` Chris Gianelloni
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=20050916203105.GB17982@nightcrawler \
--to=ferringb@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