What I'm trying to do is set this up as a one-step process without having to run
additional steps to query the repository. Since the repository is getting tagged
at the time, it should know the revisions of the files that it is tagging, and
that information could be easily displayed if an option was specified.
Thanks for the reply anyways.
Mal
Derek Scherger wrote:
> I use something like
>
> cvs -q rdiff -s -r load-tag-1 -r load-tag-2
>
> all the time compare two releases/builds. Does this not do what you
> want?
>
> Malcolm Fernandes wrote:
> >
> > Larry Jones wrote:
> >
> > > Malcolm Fernandes writes:
> > > >
> > > > Is there a global CVS command to display the revisions of the files that
> > > > are being tagged.
> > >
> > > No. Revisions are not significant in CVS and should generally be
> > > ignored: just use tags.
> > >
> >
> > We tag our load builds with an identifier specific to that load build. If I
> > could log the revisions of the files, then it would be very convenient to
> > refer to the logfile to find out whether a particular revision of a file went
> > into that particular load build. This would be more efficient than checking
> > out the tree based on the tag and then finding out the revision of a file OR
> > using 'cvs stat -v {fileName} |grep {Identifier}' for each file in question.
> >
> > Mal
> >
> > >
> > > -Larry Jones
> > >
> > > I don't think math is a science, I think it's a religion. -- Calvin
>
> --
> Cheers,
> Derek
> _____________________________________________________________________
> Derek Scherger Echologic Software Corporation
> mailto:[EMAIL PROTECTED] http://www.echologic.com
