I have a cvs repository containing code which is labelled every time we do a build. Once we were ready to make build 24 we did "cvs tag bld-1-0-24" and after modifications and releasing build 25 we did "cvs tag bld-1-0-25" (1-0 is version 1.0). Thus we have all the source code in a module tagged with build 24 and some of the code modified and tagged with build 25. I know I can use cvs log -rbld-1-0-24:bld-1-0-25 to get a log of commits between the two builds, however it lists the change that was tagged with bld-1-0-24, thus: The file "Makefile" was tagged with bld-1-0-24 for cvs revision 1.26 with a comment of "fixed bug in foo.cpp" The file "Makefile" for cvs revision 1.27 has a comment of "fixed bug in foo2.cpp" this was not tagged in cvs. The file "Makefile" was tagged with bld-1-0-25 for cvs revision 1.28 with a comment of "fixed bug in foobar.cpp" Thus the change made for build 25 was to fix a bug in foo2.cpp and foobar.cpp, however cvs log lists the commit messages for foo.cpp aswell (this was not a fix for build 25 as it went out with 24). I know I have listed the Makefile above, but this is for illustration purposes, the principle is the same for any source file. My question is how do I get a log of commits for *after* the bld-1-0-24 tag and upto and including any revisions for the bld-1-0-25 tag? Also if code has not been changed the same revision with be tagged with bld-1-0-24 and bld-1-0-25. How do I stop cvs from listing these files? Basically I am trying to provide a report of the changes that have been made between two builds of the code. If "cvs log" is the wrong thing to use, how do I do it? Regards, & thanks in advance John Scott Middleware Systems Technical Specialist IS Middleware Services Argos Ltd [EMAIL PROTECTED] ******************************************************************** The information contained in this message or any of its attachments may be privileged and confidential, and is intended exclusively for the addressee. The views expressed may not be official policy, but the personal views of the originator. If you are not the addressee, any disclosure, reproduction, distribution, dissemination or use of this communication is not authorised. If you have received this message in error, please advise the sender by using the reply facility in your e-mail software. All messages sent and received by Argos Ltd. are checked for malicious content. ********************************************************************
