From: Mattia Jona-Lasinio <mjona@lkb.ens.fr>
To: linux-8086@vger.kernel.org
Subject: Re: CVS access
Date: Wed, 2 Aug 2006 15:24:59 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.62.0608021518030.8752@localhost.localdomain> (raw)
In-Reply-To: <20060731175118.f24f2db4.nuxnet@chello.at>
On Mon, 31 Jul 2006, Petr Koval wrote:
> On Mon, 31 Jul 2006 17:29:29 +0200 (CEST)
> Mattia Jona-Lasinio <mjona@lkb.ens.fr> wrote:
>
>> The sourceforge site has change their names for CVS access. Now there is a
>> CVS access using
>>
>> cvs -d:pserver:anonymous@elks.cvs.sourceforge.net:/cvsroot/elks login
>> cvs -z3 -d:pserver:anonymous@elks.cvs.sourceforge.net:/cvsroot/elks co modulename
>
> modulename elks is accessable
> modulenames elksnet,elkscmd, etc are not
>
> pavilion CVSROOT # cvs -d:pserver:anonymous@elks.cvs.sourceforge.net:/cvsroot/elksnet login
> Logging in to :pserver:anonymous@elks.cvs.sourceforge.net:2401/cvsroot/elksnet
> CVS password:
> cvs login: authorization failed: server elks.cvs.sourceforge.net rejected access to /cvsroot/elksnet for user anonymous
> pavilion CVSROOT # cvs -d:pserver:anonymous@elks.cvs.sourceforge.net:/cvsroot/elkscmd login
> Logging in to :pserver:anonymous@elks.cvs.sourceforge.net:2401/cvsroot/elkscmd
> CVS password:
> cvs login: authorization failed: server elks.cvs.sourceforge.net rejected access to /cvsroot/elkscmd for user anonymous
The cvsroot should not be changed. the following is correct.
cvs -d:pserver:anonymous@elks.cvs.sourceforge.net:/cvsroot/elks login
cvs -z3 -d:pserver:anonymous@elks.cvs.sourceforge.net:/cvsroot/elks co modulename
where modulename is one of
elks the true elks project
elks-0.2 seems to be empty
elks-0.3 seems to be empty
elkscmd shells, editors and other stuff
elksnet sort of tcp/ip stack
elkspages seems to be the website
elksutils seems to be empty
elksweb again the website
elksweb2 still the website
Bye,
M
prev parent reply other threads:[~2006-08-02 13:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 14:09 Porting to different architectures chriscureau
2006-07-31 15:00 ` Hans
2006-07-31 15:35 ` Richard Wallman
2006-07-31 16:03 ` David Given
2006-07-31 16:24 ` Richard Wallman
2006-07-31 16:32 ` David Given
2006-07-31 17:42 ` Jody Bruchon
2006-08-01 6:49 ` Richard Wallman
2006-08-01 17:15 ` Segin
2006-07-31 19:47 ` Javier Sedano
2006-07-31 21:44 ` Alan Cox
2006-08-01 2:57 ` Tom McCabe
2006-08-01 5:27 ` Jody Bruchon
2006-08-01 13:22 ` Alan Cox
2006-08-01 14:41 ` Vikas N Kumar
2006-08-01 15:28 ` Hans
2006-07-31 15:16 ` Petr Koval
2006-07-31 15:29 ` CVS access Mattia Jona-Lasinio
2006-07-31 15:43 ` Petr Koval
2006-07-31 15:51 ` Petr Koval
2006-08-02 13:24 ` Mattia Jona-Lasinio [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=Pine.LNX.4.62.0608021518030.8752@localhost.localdomain \
--to=mjona@lkb.ens.fr \
--cc=linux-8086@vger.kernel.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