From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: Jeffrey A Law <law@cygnus.com>
Cc: egcs@cygnus.com
Subject: Re: Direct CVS Access to egcs sources
Date: Thu, 15 Jan 1998 16:30:00 -0000 [thread overview]
Message-ID: <199801142227.OAA03716@cygnus.com> (raw)
In-Reply-To: <11672.884670861@hurl.cygnus.com>
Hi,
could you setup a simple webpage which links in all the current ChangeLogs
from the cvs tree? Something like:
ChangeLog
gcc/ChangeLog
libio/ChangeLog
etc.
I think this would be quite useful.
Bye,
Franz.
At 06:54 13.01.98 , Jeffrey A Law wrote:
>
>January 12, 1998
>
>In an ongoing effort to accelerate development of egcs and provide an
>open development environment, we are making the egcs CVS source repository
>available readonly to the public at large.
>
>You'll be able to pick up the latest code whenever you want instead of
>waiting for periodic snapshots. You'll even be able to check out the
>release branch(es) since they also live in the CVS repository.
>
>If you don't already have CVS, we recommend you pick up a recent copy from
>Cyclic Software at http://www.cyclic.com .
>
>Assuming you have CVS installed on your machine you can check out the egcs
>sources with the following sequence of commands:
>
>set CVSROOT in your environment to
>
>:pserver:anoncvs@egcs.cygnus.com:/egcs/carton/cvsfiles
>
>Or alternately add "-d
:pserver:anoncvs@egcs.cygnus.com:/egcs/carton/cvsfiles"
>in the CVS commands below (place it immediately after "cvs" -- ie
>before any other cvs arguments).
>
>Issue the command "cvs login". You will be prompted for a password;
>reply with "anoncvs".
>
>Issue the command "cvs co egcs" to check out the egcs sources.
>
>Once you've got the repository checked out "cvs update" will sync your
>local sources with those in the repository. See the CVS manual for
>additional information on how to use CVS.
>
>
>Enjoy!
>
next prev parent reply other threads:[~1998-01-15 16:30 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-13 4:52 Jeffrey A Law
1998-01-14 8:18 ` Oleg Krivosheev
1998-01-14 8:42 ` Jeffrey A Law
1998-01-15 16:06 ` Joe Buck
1998-01-15 16:30 ` Jeffrey A Law
1998-01-16 1:51 ` Joe Buck
1998-02-08 0:29 ` Jeffrey A Law
1998-02-08 7:13 ` Gerald Pfeifer
1998-02-08 8:57 ` Dave Love
1998-02-08 10:14 ` Jeffrey A Law
1998-02-08 13:23 ` H.J. Lu
1998-02-08 15:38 ` Jeffrey A Law
1998-02-08 15:20 ` H.J. Lu
1998-02-08 15:38 ` Jeffrey A Law
1998-02-08 18:35 ` Todd Vierling
1998-02-08 15:38 ` Bryan W. Headley
1998-01-17 22:30 ` Raja R Harinath
1998-01-15 16:30 ` Robert Lipe
1998-01-16 2:26 ` Jeffrey A Law
1998-01-15 16:30 ` Franz Sirl [this message]
1998-01-17 1:40 ` Robert Lipe
1998-01-17 22:30 ` Joseph H. Buehler
1998-01-19 2:25 ` Robert Lipe
1998-01-19 2:30 ` Fred Fish
1998-01-19 2:30 ` Jeffrey A Law
1998-01-20 4:00 Mike Stump
[not found] <199801142227.OAA03715@cygnus.com>
1998-01-23 0:20 ` Jeffrey A Law
1998-01-23 11:15 ` Franz Sirl
[not found] <199801231742.JAA01350@cygnus.com>
1998-01-23 9:47 ` Jeffrey A Law
[not found] <19980209020929.50632@cerebro.laendle>
1998-02-08 22:42 ` Jeffrey A Law
1998-02-09 19:49 ` Joern Rennecke
1998-02-09 21:34 ` Jeffrey A Law
1998-02-11 10:25 ` Marc Lehmann
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=199801142227.OAA03716@cygnus.com \
--to=franz.sirl-kernel@lauterbach.com \
--cc=egcs@cygnus.com \
--cc=law@cygnus.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).