Re: cvs log: incorrect usage?

[Todd Denniston]

Bob McCallister wrote:
> 
> You misunderstood me.  The librarian is presented with a screen that lists
> all the projects.  He clicks on a project and is presented with a list of
> tags (in theory).  He then chooses which tag and *then* the project is
> checked out to its target directory.
> 

I suppose there are processes in place to help him choose the correct tag
from the list.

> As for cvs rlog - I get a deprecated warning (use log) and I got an error
> that the directory was not found.  My $CVSROOT was set accordingly.

try `cvs --version` 
the "rlog command is deprecated" was fixed/changed between cvs-1.11 and 
cvs-1.11.1, it really is time for you to upgrade, there have been numerous
fixes including security since then.

> 
> > 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?
> >
<SNIP>
-- 
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane) 
Harnessing the Power of Technology for the Warfighter