DO NOT REPLY [Bug 13510] - CvsChangeLog should accept a branch as an optional parameter
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13510. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13510 CvsChangeLog should accept a branch as an optional parameter [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED Target Milestone|--- |1.6.1 --- Additional Comments From [EMAIL PROTECTED] 2004-01-28 23:19 --- I have submitted changes in for this bug in HEAD and in the ANT_16_BRANCH. A new task cvsversion has been added to allow to detect whether the -S option is supported. Also the task cvschangelog has been changed programmatically to extend AbstractCvsTask. The branch can be entered as the tag attribute. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 13510] - CvsChangeLog should accept a branch as an optional parameter
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13510. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13510 CvsChangeLog should accept a branch as an optional parameter [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] AssignedTo|[EMAIL PROTECTED] |[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2004-01-22 09:27 --- I am going to start working on this issue concretely as soon as I can, with the aim of getting this into the ant 1.6.1 beta. Cheers, Antoine - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 13510] - CvsChangeLog should accept a branch as an optional parameter
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13510. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13510 CvsChangeLog should accept a branch as an optional parameter --- Additional Comments From [EMAIL PROTECTED] 2003-07-27 22:00 --- Just noticed: The changelog task itself skips any files that has no log entries. And the unwanted info about added files on other branches always show up without any actual log entries (selected revisions: 0) in the log, so as far as I can see they should not be any problem. In that case adding branch info is a very straighforward task. I have done so on my ant source installation and it works fine. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 13510] - CvsChangeLog should accept a branch as an optional parameter
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13510. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13510 CvsChangeLog should accept a branch as an optional parameter --- Additional Comments From [EMAIL PROTECTED] 2003-04-23 13:08 --- I've reproduced the problem on the latest cvs version (1.11.5) and it seems as the only way to get around this is by using the -S flag. This flag was added in version 1.11.2 which was released in april 2002, so you'll need a fairly new cvs server to get this working. Maybe the ant task can check for the cvs server version before attempting to set a branch property, and issue a warning if the server is prior to 1.11.2 ?
DO NOT REPLY [Bug 13510] - CvsChangeLog should accept a branch as an optional parameter
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13510. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13510 CvsChangeLog should accept a branch as an optional parameter --- Additional Comments From [EMAIL PROTECTED] 2003-04-17 15:16 --- Simon, what version of CVS are you using? This is a know issue with cvs that has been resolved. Is upgrading your version of cvs an option. Passing the -S option may be useful as well (doesn't show files that have 0 revisions selected). Eg cvs log -S -rbranch_name.
DO NOT REPLY [Bug 13510] - CvsChangeLog should accept a branch as an optional parameter
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13510. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13510 CvsChangeLog should accept a branch as an optional parameter --- Additional Comments From [EMAIL PROTECTED] 2003-03-18 22:08 --- I attempted to implement this RFE a few weeks ago (it should be simple), but couldn't make the underlying CVS client actually give me the logs I wanted. If I do a cvs log -rSOME_BRANCH it mostly works, except that it provides logs for files that are not *on* that branch. I suspect I've got a conceptual mismatch, but maybe my flounderings will be useful to someone else :) Example: In a directory, there is a file A in HEAD with revision 1.5. A branch TEST_BRANCH is made at this point, and further changes are made to A on that branch (revision 1.5.2.1). Meanwhile, on HEAD other changes are made to A (revision 1.6) and a new file B is added (revision 1.1). If I do a cvs log -rTEST_BRANCH in that directory, I see change A:1.5.2.1 (correct!) and change B:1.1 (not wanted!). *shrug*
