Bob McCallister wrote: > > But what if I want to know what tags are available for a given project? We > have a "librarian" who checks out tagged versions of projects to their > production location. That librarian has no idea who is working on the > project and therefore doesn't know where the working copies reside. Are > you saying the librarian should have to check out a copy just to get the > tags?
1) You already indicated the "librarian" HAS a checked out copy as part of thier job. :) the log command IIRC lists ALL revisions and tags, not just the one that was used to checkout a version. 2) as larry mentioned rlog (on current versions) will work without a checked out copy. 3) how is your libriarian to know what one they should be checking out anyway? Surely your process includes passing along the current production tag, correct? > > > coach24 wrote: > > > > > > If my repository is /usr/local/cvs, am I not supposed to be able to do > > > this: > > > > > > cvs log /usr/local/cvs/project/file.py,v > > > > > > I get the *PANIC* administration files missing error every time. There > > > is a CVS directory for that project. This command doesn't work on two > > > different machines in three different repositories. What gives? > > > > ClueX4 yourself until you no longer feel the need to use commands directly > > on the repository files after you set it up, with _one_ exception the > backup > > routine. :) > > > > > > > > Now, if the cvs log command is only supposed to be used in checked out > > > sandboxes, fine. > > > > This is a true statement. > > > > > What can I do then to be able to parse repository > > > files for tags? > > > > In a sandbox: > > cvs log file.py |grep -A25 "symbolic names:" > > > > everything between "symbolic names:" and "keyword substitution:" is a > > relationship between a tag and a file revision. > > Does this help? > > > > > > > > Thanks for your help, > > > Bob > > > > > > PS cvs history on the same pathname works just fine. > > um, don't do that either. :) > > -- > > Todd Denniston > > Crane Division, Naval Surface Warfare Center (NSWC Crane) > > Harnessing the Power of Technology for the Warfighter > > > > ______________________________________________________________________ > > This e-mail has been scanned by MCI Managed Email Content Service, using > Skeptic(tm) technology powered by MessageLabs. For more information on > MCI's Managed Email Content Service, visit http://www.mci.com. > > ______________________________________________________________________ > > -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter _______________________________________________ Info-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/info-cvs
