Stephane Eranian wrote:
Will,

On Mon, Aug 21, 2006 at 04:09:29PM -0400, William Cohen wrote:

I tracking the development of libpfm and pfmon via the cvs repositories. One of the things that was nice in packages such as GCC, GDB, OProfile, and other open source software was to have the ChangeLog record what changed On could just look at the ChangeLog file and see what what files one might need to look at more closely. This file would be automatically downloaded when doing a "cvs -d -P" on the code.

Kevin's suggestion of cvsps was useful. That returns the information information that I am interested in: what is checked in together.

What does cvs -d -P exactly do?

"cvs -d -P" in the cvs directory for the package does a update of the current directory and the children directories (-d) and prunes the empty files (-P).

There is a comment in the libpfm mentioning that this will no long be updated:

2006-08-21 Stephane Eranian <[EMAIL PROTECTED]>
       This file will not be updated anymore,  Refer to
       SF.net CVS log for diff information



Yes, I realize I was not doing a very good job at updateing the Changelog
for every modifications I made or received. Given that cvs commit forces me
to enter a description, I thought it would be fairly easy to pull
the information from CVS.
Here is one thing you can do when inside the CVS-pulled source tree:
        $ cvs log '-d>060625' -N

This command dumps the log information for all modifications after 06/06/25.
This is not a short and concise as I'd like it to be. It may be possible
to write a script to present this better.


How does one get a view of the group of files checked in together for some change? That was the nice thing about having the ChangeLog, one entry listed all the files that were checked in together. How does one get a similar view with the SF.net CVS log?


If there is enough complaints about this, then I'll revisit my decision!

I wasn't complaining. :) I just wanted to make sure there was a easy way to get get the equivalent information to the old ChangeLog. The "cvs log" slices things up and doesn't give the information in a convienent format. It gives the information on a per file basis.

-Will

_______________________________________________
perfmon mailing list
[email protected]
http://www.hpl.hp.com/hosted/linux/mail-archives/perfmon/

Reply via email to