info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: a tag layer on cvs


From: Teala Spitzbarth
Subject: RE: a tag layer on cvs
Date: Tue, 8 Jan 2002 15:04:49 -0800

Sounds like a fair chunk of work.  The difficulty of course
being, what are the best practices that will work for most
individuals and groups?

Not clear to me that a layer ontop of CVS had signficant
advantage over a re-write? Have you looked at Subversion?
http://subversion.tigris.org/

Cheers,
Teala

-----Original Message-----
From: Matthew Herrmann [mailto:address@hidden
Sent: Monday, January 07, 2002 3:49 PM
To: CVS Mailing List
Subject: a tag layer on cvs


hi all,

what do people think about the idea of a project which sits on top of
cvs
and provides another level of abstraction to branching, merging,
revision
management etc.

The idea would be to have responsibilities divided up in this hierarchy:

- CHANGELOG (eventually could use TAGSYSTEM to do all the special tag
stuff)
- TAGSYSTEM (no magic revision numbers -- all hidden, disallows
branching on
individual files, branching automatically creates the branchpoint and
branch
tag, allows complex rules for generating diffs, merging generates
mergepoint
tags etc., checkouts, tags etc.)
- CVS (revision, tag, logistics of branch management, merging etc.)

TAGSYSTEM would effectively be a system which concretises "best
practice"
which is of course another way of saying "magical rules which much be
obeyed
so things work as expected". The reality is that CVS can do basically
everything that other systems like clearcase can, with the exception of
graceful directory and file renames, only, people need to do things "the
right way". This would remove that "right way" element. It would become
a
"command".

CVS then no longer needs to concentrate on providing user interface type
features, it basically operates as a versioned file management system.
Instead of every shop making their own custom scripts to do things,
there is
a 'recommended' shell which does what most people do anyway --
mergepoint
tags etc.

My idea was to do it in a compilable scripting language, (python -- my
choice, perl, vb (just kidding)) and that it would call cvs behind the
scenes.

is this way off? or are people interested?

Regards,

Matthew Herrmann
--------------------------------------
Far Edge Technology
Level 11, 80 Mount St
North Sydney NSW 2060
Australia

Ph: 02 9955 3640
Mob: 0404 852 537


_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs



reply via email to

[Prev in Thread] Current Thread [Next in Thread]