From: Samuel Tardieu <sam@inf.enst.fr>
Subject: Re: CVS'r'us
Date: 05 Mar 1997 12:29:13 +0100 [thread overview]
Message-ID: <qw64teqmvau.fsf@esmeralda.enst.fr> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 05 Mar 1997 07:38:09 +0100
>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
Lars> Thanks to Steven's RCS repository of Gnusae past (along with my
Lars> archive of old (ding) patches and releases) I've now constructed
Lars> a CVS repository of all Gnus 5 releases -- ever. (Well, I'm
Lars> missing a few releases here and there.)
Great! The next step is to arrange an anonymous (or controlled)
read-only access for those of use who are willing to get incrementally
the latest revision or see at what point things have changed :-)
I know of some people who have done this already. One exemple is the
maintainer of phpfi. Here is an extract of the README file:
"
Getting Updates
---------------
Entire new distributions of the package are made available frequently
in the file archive at http://www.vex.net/php/files
If you don't like re-installing every time you want to update your
package, or if you are a programmer and want to make sure you always
have the latest bleeding-edge version of the package, get a package
called CVS. It is available at prep.ai.mit.edu:/pub/gnu. Get version
1.7 or later. Compile and install this package. Make sure you enable
client support. Check the cvs-1.7/src/options.h file and verify that
AUTH_CLIENT_SUPPORT is defined.
Now type the following:
cvs -d :pserver:cvsread@vex.net:/u/local/src/repository login
When it asks you for a password enter: phpfi
Then type:
cvs checkout phpfi
This will create a phpfi directory in your current directory. It will
take a bit of time, especially if your network connection is slow.
But once it is done, you will have an up to date copy of the master
CVS source tree. You can then at any time cd into this directory and
type:
cvs update
to update your source tree to be in sync with the master tree.
[...]
Keep in mind that the CVS version may not always compile, or if it does
compile, it may not be stable. The CVS version is a development version
and should be treated as such.
"
Sam
--
Samuel Tardieu -- sam@inf.enst.fr
next prev parent reply other threads:[~1997-03-05 11:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-03-05 6:38 CVS'r'us Lars Magne Ingebrigtsen
1997-03-05 7:49 ` CVS'r'us Steven L Baur
1997-03-05 9:56 ` CVS'r'us Lars Balker Rasmussen
1997-03-05 7:49 ` CVS'r'us Steven L Baur
1997-03-05 11:29 ` Samuel Tardieu [this message]
1997-03-06 3:59 ` CVS'r'us Lars Magne Ingebrigtsen
1997-03-06 10:06 ` CVS'r'us Kai Grossjohann
1997-03-06 19:06 ` CVS'r'us Lars Magne Ingebrigtsen
1997-03-06 20:38 ` CVS'r'us Scott Blachowicz
1997-03-06 20:49 ` CVS'r'us Kai Grossjohann
1997-03-06 23:00 ` CVS'r'us Lars Magne Ingebrigtsen
1997-03-07 9:57 ` CVS'r'us Kai Grossjohann
1997-04-03 17:24 ` CVS'r'us Brian Edmonds
1997-04-04 19:26 ` CVS'r'us Lars Magne Ingebrigtsen
1997-04-04 21:06 ` CVS'r'us Steven L Baur
1997-04-05 10:46 ` CVS'r'us Lars Magne Ingebrigtsen
1997-04-06 1:09 ` CVS'r'us Brian Edmonds
1997-04-06 17:44 ` CVS'r'us Lars Magne Ingebrigtsen
1997-04-07 1:51 ` CVS'r'us Tony Bennett
1997-04-08 20:59 ` CVS'r'us Lars Magne Ingebrigtsen
1997-04-06 13:58 ` CVS'r'us Kai Grossjohann
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=qw64teqmvau.fsf@esmeralda.enst.fr \
--to=sam@inf.enst.fr \
/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 NNTP newsgroup(s).