You can't do it with CVS alone. The output of "cvs log" can be parsed and reformatted into a better report, but doing so is not foolproof due to the way the rlog formats its output. (User comments can look like the syntax RCS uses to identify versions.)
Take a look at the rinfo and lmerge programs. They're designed to produce automatic reports and will take you a long way to getting what you want, but you'll have to go the last 20% to produce a list of files and version ranges to feed to rinfo. Both of these programs are available at http://www.wakawaka.com/source.html >--- Forwarded mail from [EMAIL PROTECTED] >Im new to the group, and ill get straight to the point. >Im requested to get the checkin comments of branches and tags and make = >them into some sort of releasenote.txt. >-------------------------- >Say I have a module called FOO. >And I branched it to FOO-branch >How would I get the check in comments of FOO-branch between 9/1 and = >9/30.=20 >Mind you, that im only looking for info on that branch, and not the = >whole module and other branches related to it. >Im having the hardest time trying to find a command that will just give = >me the info I need, instead of giving me the log of the whole module = >from the main trunk. >This is my first guess: >cvs log -d"2002-9-1<2002-9-30" -rFOO-branch FOO>>c:\work\history.txt >which does nothing other than get me the whole main trunk of the tree = >and not the branch. Many many unrelated changes are poping up. >--- End of forwarded message from [EMAIL PROTECTED] _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
