Hello Mark,
I thought I mentioned that in one of my previous mails, though maybe it
wasn't very
clear. It's true that lstag is limited to the directory tree you are *in*
when you run it.
I concede that the online help printed by lstag might better be updated.
That basically means that lstag is limited by the organization of the
modules and
projects. A habit of mine is to always create a toplevel dir, even for
repositories
with a single project. That way I can always check out the toplevel dir
and have
easy access to the entire project by recursing down the tree.
So for a project with two components, say foo and bar, I would have:
CVS repository instead of CVS repository
| |
+--- projectname +--- foo
| |
+--- foo +--- bar
|
+--- bar
So I'd usually check out 'projectname' and run lstag -l in there
to get the list of tags used by that project. :)
Erik
"Zieg, Mark" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
09/26/2002 05:24 PM
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
Subject: RE: List of CVS Tags
Um, you might want to warn people that it only lists tags associated with
files that are in or below the current directory. If there are tags in
your
project which were not applied to your current tree, then you won't be
alerted to their existence.
If you have local access to your cvsroot, you should be able to get a list
of ALL tags used in the module with this:
find /usr/local/cvsroot/PRISM -name *,v | xargs perl -n -e 'if($s){last
unless($t)=/(\S+):/;print"$t\n";}else{$s=/^symbols/;}' | sort -u
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
