> Why is it again you are using the $Log:$ for anything anyway, i.e., > what is your purpose for having Log in your files? (often times this > group can come up with a much better way to get to the ends you desire.)
OK, good point. As manager of a team, I occasionally have needed (when using VSS [fx:spit] in a previous company) to track what was changed and why. With Log, a simple grep through the files was all that was needed. I'm the first to admit that I'm not using the full features of CVS yet - like merging branches etc, so I haven't come across the issues that you describe. And also, I'm only beginning to realise the full use of the annotate command. It provides what I need directly - to track down who changed a line of code. Then I can extract log comments from cvs for that revision and see why they were done. So probably I don't really need Log in the header anyway. > It is only the comments that you can get back better using `cvs log` or > cvs2cl. Thanks for the tip. I downloaded cvs2cl but have some problems with it - even with the latest Perl (running under Windows 2000) the second line had problems. I commented it out; now I get output like: .... server: Logging system/web server: Logging system/web/cgi-bin server: Logging system/webserver server: Logging system/webserver/Widgets but then it just hangs. No activity. I ran it with a blank command line, then tried --stdout but nothing happens. Any ideas? I speak Python/C++ but not Perl, so don't know the best way to go about debugging it. If I can get this to run it would be great to set up the auto reports on checkins, like the gentoo site http://www-106.ibm.com/developerworks/web/library/us-gentoo4/?dwzone=web;# h13764 Hugh _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
