Erlang Development Environment

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Erlang Development Environment

Mostly historical reasons. It started off with just Sean hacking away in the
dark ages and suddenly we have so much code under RCS now and none of us
have the time to try anything new!

Thats why I'm keen to see CCviewer being made generic enough to handle any
version control system - even no version control system.


> -----Original Message-----
> From: David Gould [mailto:davidg]
> On Wed, Mar 07, 2001 at 04:30:13PM +0100, Ulf Wiger wrote:
> > On Wed, 7 Mar 2001, Chandrashekhar Mullaparthi wrote:
> >
> > >We use RCS. I tried to customise CCviewer but gave up very fast :)
> > >Can we do a RCSViewer too?!
> >
> > Sure, why not!
> > I have nothing else to do. (:
> You get lucky here, CVS uses RCS to store its files. So if it can work
> for RCS, it will also mostly work for CVS. Of course, CVS adds another
> layer of features, so there might be more capability in CVS mode.
> Oh, Chandru, why do you use RCS instead of CVS? Just curious.
> I use RCS alone
> when I play sysadmin, so if I mess up configuring something, I have a
> fallback plan, and also to document changes made to a system. But for
> software development, CVS seems much nicer unless you have
> only a few files.

This email (including attachments) is confidential.  If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents.  We cannot accept liability for any breaches of
confidence arising through use of email.  Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions.  We will not accept responsibility for any commitments
made by our employees outside the scope of our business.  We do not warrant
the accuracy or completeness of such information.