From: Mo DeJong <supermo@bayarea.net>
To: sourcenav <sourcenav@sources.redhat.com>
Subject: Re: New CVS module to checkout.
Date: Thu, 21 Feb 2002 01:51:00 -0000 [thread overview]
Message-ID: <20020221012244.3c9de5ce.supermo@bayarea.net> (raw)
In-Reply-To: <20020220161150.3c173398.supermo@bayarea.net>
On Wed, 20 Feb 2002 16:11:50 -0800
Mo DeJong <supermo@bayarea.net> wrote:
> On Wed, 20 Feb 2002 16:04:53 -0800
> Ian Roxborough <irox@redhat.com> wrote:
>
> > Hi,
> >
> > I've added a new module to the sources.redhat.com:/cvs/src
> > root to make life easier for people checking SN out of CVS.
>
> That CVSROOT was not quite right. It should be:
We should really add this info to the download page. Appended
is a patch to do just that. Also, I found out that there is a cvsweb
viewer that can be used to view the SN code. I included a link
to it in the patch. The patch also fixes a couple of other minor
little mistaked on the download page.
cheers
Mo
2002-02-28 Mo DeJong <supermo@bayarea.net>
* download.html: Fixup wording so that it does
not sound like the most recent release was
the "last" release. Don't mention HPUX
since we do not provide a binary for it.
Describe how to download the latest code via
CVS and include cvsweb links for gdb and
the snavigator CVSROOTs.
--- /tmp/download.html Thu Feb 21 01:16:10 2002
+++ download.html Thu Feb 21 01:06:52 2002
@@ -66,9 +66,9 @@
<H1>Downloading
Source-Navigator<FONT SIZE="-2"><SUP>TM</SUP></FONT></H1>
- <P>Version 5.0 is the last stable release. You can download
+ <P>Version 5.0 is the most recent stable release. You can download
source for stable releases. You can also download pre-built
- binaries for Solaris, HPUX or Windows.</P>
+ binaries for Solaris or Windows.</P>
<P>Development releases are not guaranteed to be stable;
they are snapshots of what the Source-Navigator team is
@@ -83,6 +83,33 @@
<a href="http://mirrors.rcn.net/pub/sourceware/sourcenav">
http://mirrors.rcn.net/pub/sourceware/sourcenav</a>
</p>
+
+ <p>
+ <b>CVS Access</b><br>
+ The bleeding edge development version is always available
+ via CVS. The following instructions assume a C shell and
+ a CVS command line client.
+
+ <pre>
+setenv CVSROOT :pserver:anoncvs@anoncvs.cygnus.com:/cvs/src
+cvs login
+(password is "anoncvs")
+cvs checkout sn-support
+
+setenv CVSROOT :pserver:anoncvs@anoncvs.cygnus.com:/cvs/sourcenav
+cvs login
+(password is "anoncvs")
+cvs checkout snavigator
+ </pre>
+
+ A cvsweb interface is also available. With it, you can browse the code
+ that makes up the
+ <A HREF="http://sources.redhat.com/cgi-bin/cvsweb.cgi/?cvsroot=src">sn-support</a>
+ and
+ <A HREF="http://sources.redhat.com/cgi-bin/cvsweb.cgi/?cvsroot=sourcenav">snavigator</a>
+ modules.
+ </p>
+
</TD>
</TR>
</TABLE>
next prev parent reply other threads:[~2002-02-21 9:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-20 16:12 Ian Roxborough
2002-02-20 17:51 ` Mo DeJong
2002-02-21 1:51 ` Mo DeJong [this message]
2002-02-21 14:48 ` Eray Ozkural
2002-02-21 15:35 ` Ian Roxborough
2002-02-22 0:16 ` Eray Ozkural
2002-02-22 2:43 ` Mo DeJong
2002-02-21 16:43 ` Mo DeJong
2002-02-21 18:17 ` Eray Ozkural
2002-02-22 8:16 Doug Fraser
2002-02-22 10:05 ` Eray Ozkural
2002-02-22 11:08 ` Gilles J. Seguin
2002-02-22 13:07 ` Ian Roxborough
2002-02-22 10:26 Doug Fraser
2002-02-22 13:55 ` Khamis Abuelkomboz
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=20020221012244.3c9de5ce.supermo@bayarea.net \
--to=supermo@bayarea.net \
--cc=sourcenav@sources.redhat.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).