RE: find changeset for a file

[Arthur Barrett]

Sandeep,

Note: CVSNT (yes it works on linux too, LGPL) has a 'commitid' property
- all files with the same 'commitid' were committed together.  CVSNT
also has 'bugid' which is a user defined change set that can occur on
multiple commits.

Todd's suggestion of similar date/time with same comment is great -
until you have a team that has overlapping commits with the same "blank"
message (or some 'standard text').  I see this a lot...

Regards,


Arthur


> -----Original Message-----
> From: 
> address@hidden 
> [mailto:address@hidden
> org] On Behalf Of sandeepk1611
> Sent: Thursday, 17 February 2011 9:26 AM
> To: address@hidden
> Subject: CVS: find changeset for a file
> 
> 
> 
> Hi, 
> 
> I am doing some research with CVS logs. I used the cvs rlog 
> command to get
> the revision information for the CVS files in a module. I was 
> wondering
> whether there is some way I can also know, for each revision, 
> how many other
> files were modified along with the current file. 
> 
> For example, 
> 
> Currently a sample rlog -N command output looks like this, 
> 
> file1
> head: 1.33
> branch:
> locks: strict
> access list:
> keyword substitution: o
> total revisions: 35;  selected revisions: 2
> description:
> ----------------------------
> revision 1.30
> date:date1;  author: author1;  state: Exp;  lines: +2 -2;
> text1
> ----------------------------
> revision 1.29
> date: date2;  author: author2;  state: Exp;  lines: +1 -1;
> text2
> ....
> 
> I was wondering if for each revision, I can also get information, 
> 
> Changeset: ###(some number)
> 
> If I cannot get it directly by rlog command, is there any 
> other command by
> which I can get this information? 
> 
> Any help will be be very useful. 
> 
> Thanks,
> Sandeep
> -- 
> View this message in context: 
> http://old.nabble.com/CVS%3A-find-changeset-for-a-file-tp30939
494p30939494.html
Sent from the Gnu - Cvs - Info mailing list archive at Nabble.com.