Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Zsh and CVS
- X-seq: zsh-users 1513
- From: Scott RoLanD <shr@xxxxxxxxxxxxx>
- To: zsh-users@xxxxxxxxxxxxxxx
- Subject: Re: Zsh and CVS
- Date: Mon, 4 May 1998 16:47:32 -0700
- In-reply-to: <980418112151.ZM4129@xxxxxxxxxxxxxxxxxxxxxxx>; from Bart Schaefer on Sat, Apr 18, 1998 at 11:21:51AM -0700
- Mail-followup-to: zsh-users@xxxxxxxxxxxxxxx
- References: <199804180953.JAA08829@xxxxxxxxxxxxxxxxxxxxxxxxxx> <980418112151.ZM4129@xxxxxxxxxxxxxxxxxxxxxxx>
On Sat, Apr 18, 1998 at 11:21:51AM -0700, Bart Schaefer wrote:
> On Apr 18, 9:53am, TGAPE! wrote:
> } Subject: Re: Perl and ZSH
> }
> } >On 17 Apr 1998, Karsten Thygesen wrote:
> } >
> } >btw is there a cvs repository for zsh?
> }
> } Not that I know of[1]; what's wrong with RCS? You have it on your
> } system if you have CVS. Since CVS uses RCS to do its work, it should be
> } trivial to convert.
> }
> } [1] Though Bart Schaefer might know better.
>
> I don't know of any cvs repository for zsh either (well, except my own,
> which is only 3.0.x and littered with local experiments and selectively-
> applied patches from zsh-workers).
>
> You can make RCS'd sources accessible through CVS just by dropping the ,v
> files into a directory tree under a new or existing CVS repository root;
> but manipulating any RCS branch revisions probably won't work becaus CVS
> uses a very particular branch numbering scheme. To do it "right" you'd
> have to check out each RCS revision and then import it into CVS, to make
> a CVS revision history that matches the original RCS one.
>
> You'd be better off to simply select a stable starting point, import that,
> and begin to use CVS exclusively from there.
>
As an aside I would encourage everyone to look into using Perforce
(www.perforce.com) for work on free projects (and commercial too; but
it is free for free projects). I find it much more usable the CVS.
RoLanD
--
Just a happy user.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author