public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Thomas <zander@javalobby.org>
To: mauve-discuss@sources.redhat.com
Cc: "Stephen Cheng" <scheng@innaworks.com>
Subject: Re: Mauve verify CVS access
Date: Thu, 15 Jul 2004 12:31:00 -0000	[thread overview]
Message-ID: <200407151431.11236.zander@javalobby.org> (raw)
In-Reply-To: <MFEHKCABJDFCMAIGKEOOIECLDFAA.scheng@innaworks.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 14 July 2004 06:00, Stephen Cheng wrote:
> Hello guru,
>
> I am trying to access the CVS repository of Mauve project the Verify
> component through CVS access, by following the instructions on
> http://sources.redhat.com/mauve/cvs.html. However it appears that the
> repository does not exist. I wonder whether you could give me any pointers.
>
> Do I need any special rights etc?
> Is the repository I used below correct?
>
> Here is the CVS command I used:
> cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/verify login
>
> Thanks,
> Stephen

The Mauve CVS repository does not have such a module; I honestly must say that 
I don't even know what you mean with the 'Verify component'..

The command you pasted is also not found on the webpage you linked to.

What were you trying to do? Did the command examples on the cvs page not work 
for you?

- -- 
Regards
Thomas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFA9nkOCojCW6H2z/QRAuA4AKCUR9CzBThuw/3M/fLDa7q53HihBgCfXu9m
OrCeRmEJsVal+PbFUseXWqo=
=pFlz
-----END PGP SIGNATURE-----

  reply	other threads:[~2004-07-15 12:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-14  4:00 Stephen Cheng
2004-07-15 12:31 ` Thomas [this message]
2004-07-16 11:48   ` James Damour
2004-07-16 12:28     ` Thomas Zander

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=200407151431.11236.zander@javalobby.org \
    --to=zander@javalobby.org \
    --cc=mauve-discuss@sources.redhat.com \
    --cc=scheng@innaworks.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).