Re: find changeset for a file

Arthur Barrett wrote, On 02/18/2011 02:55 AM:
> 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.
> 

Out of curiosity please confirm, the 'commitid' only really exists if you have been using CVSNT
since 'commitid' was added as a capability?
i.e. I can't take a normal CVS repo and drop it in under CVSNT and get 'commitid' correct?

> 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...
> 

*I* have been _fortunate_ enough that A) all my projects have forced a comment at commit time, B)
Appropriately disciplined anyone who did not use a reasonable checkin comment.  Our biggest problem
is when folks checkin ONE FILE at a time instead of a coherent checkin of the tree (with
individualized comments on EACH file) [has me reaching for my LART, by just thinking about it again].
So I can see what you are talking about, I have just only seen it polar opposite in my environment.

> Regards,
> 
> 
> Arthur
> 
> 


-- 
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter