[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Communicating through the VC tool

From: <andy.glew_at_amd.com>
Date: 2004-04-03 00:23:28 CEST

> > An example of why I want the ability to
> > see all branches from the trunk:
> > Here's my traditional CVS usage model:
> >
> > (1) I check out a module (subtree) from the trunk.
> > (2) I ask myself "who's working on this module?".
> > I run cvs log | cvs2cl.pl
>
> Just an aside - what is cvs2cl.pl - it's not something I've
> heard of before (but perhaps that's because I've never used CVS?)

"cvs log" provides log messages on a per file basis.
Which is somewhat annoying when you have 100 files,
each checked in with the same log message.

Quite a while back, actually before CVS, I wrote
rcslog-merge, which factors out the common checkin
messages, so that you see each message once and a list of
the files it applies to - along with symbolic tag
names, branch names, etc.
Mike Fetterman maintained rcslog-merge for years.
rcslog-merge worked when applied the CVS repositories,
which are really just trees of RCS files.

When CVS came along, somebody - well, bless my heart,
my copy says Karl Fogel - developed a similar script,
cvs2cl.pl, which does common subexpression elimination
on the cvs log messages and produces the much more
readable text in standard GNU ChangeLog format.

Karl: if you are the original author of cvs2cl.pl,
then we corresponded about it years ago. Good to
meet you again. Sorry to have pissed y'all off so much.

(Heck, even my "we're stuck with each other" email, which was
supposed to be a peace offering, pissed y'all off.)

---
Anyway, bottom line:
cvs2cl.pl, rcslog-merge, etc., take the per-file
all-version log messages of RCS and CVS, 
and create a global all-file, all-versions
view of the history.
Because of hierarchy,
per-subtree, all-file, all-versions
is a possibility.
By comparison, svn log provides a 
all-file per-"path-of-versions" 
view of the history.
Also per-subtree, all-file, per-"path-of-versions"
And my complaint is that 
per-subtree, all-file, all-versions
can only be obtained with svn by
getting the
all-subtree, all-file, all-versions
report, and then
performing a transitive closure
graph walk on it - not a simple 
grep.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Apr 3 00:24:05 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.