RE: cvs history with -r

[Jim.Hyslop]

Murugaiyan, Natarajan [IT] wrote:
> > The cvs command I am using is
> >     cvs history -c -p btec -a -r S8PHASE1
> > 
> > This command lists revisions committed on branch S8PHASE1 on 
> > module btec,
> > but also lists revisions committed on the trunk.
> > 
> > Is something wrong with my command or is this a CVS problem?
> >>The problem is, -r has a different meaning for "history" 
> than it does for
> >>other commands. So, you're issuing the wrong commands.
> 
> According to the usage of 'cvs history':
>       -r <rev/tag>    Since rev or tag(looks inside RCS files)
> That is what I want, give me all commits since -r S8PHASE1 
> was branched.
> 
> What is the 'different meaning' of -r option with 'cvs history'?
Sorry, I misread the Cederqvist - its meaning is not that different.

I suspect the 'history -r' does not respect branches - i.e. it may be
strictly chronological, showing everything that was checked in after the
date that tag X refers to. I'm guessing here, so I could easily be wrong.

> > Use the log command.
> 
> I want to run the following command to see if it would get 
> the report I
> was not able to get using 'cvs history'
>       cvs log -R -rS8PHASE1 -s <state>
> but could not find different possible values for <state> in 
> CVS documentation.
That's because "state" is whatever *you* define it to be. You set the state
using the 'cvs admin -s' command.

> What is the equivalent 'cvs log' command I can try?
RTFM: http://www.cvshome.org/docs/manual/cvs-1.11.7/cvs_16.html#SEC142

Pay attention to the various forms the -r option can take.

-- 
Jim Hyslop 
Senior Software Designer 
Leitch Technology International Inc. (<http://www.leitch.com/>) 
Columnist, C/C++ Users Journal (<http://www.cuj.com/experts>)