From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Getting sources from CVS
Date: Tue, 10 Aug 2004 09:31:56 -0400 [thread overview]
Message-ID: <1092144715.21441.28.camel@localhost> (raw)
In-Reply-To: <10171.81.34.135.147.1092122780.squirrel@isildur.s3os.net>
[-- Attachment #1: Type: text/plain, Size: 552 bytes --]
On Tue, 2004-08-10 at 03:26, shadow@s3os.net wrote:
> Hi we are not gentoo developers and we want to get catalyst source code from
> gentoo CVS.
>
> We need the catalyst latest resolved bugs from CVS.
>
> Is there any (readonly) public account to do it ?
There is no way to get access to our CVS unless you are a developer.
You can grab a snapshot I just made for you from
http://dev.gentoo.org/~wolf31o2/catalyst
--
Chris Gianelloni
Release Engineering QA Manager/Games Developer
Gentoo Linux
Is your power animal a penguin?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-10 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 7:26 [gentoo-dev] Getting sources from CVS shadow
2004-08-10 13:31 ` Chris Gianelloni [this message]
2004-08-10 13:45 ` John Davis
2004-08-10 23:21 ` Tom Knight
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=1092144715.21441.28.camel@localhost \
--to=wolf31o2@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