Difference between revisions of "CVS"
From Apache OpenOffice Wiki
(→I can't checkout with a certain tag) |
|||
| Line 14: | Line 14: | ||
[[http://qa.openoffice.org/issues/show_bug.cgi?id=23306 IssueZilla 23306]] | [[http://qa.openoffice.org/issues/show_bug.cgi?id=23306 IssueZilla 23306]] | ||
| + | |||
| + | ==== how to track the patch code of a issue which has been fixed and integrated ? ==== | ||
| + | (e.g) The issue 69010, belongs to the CWS impress110, has been integrated into m192. | ||
| + | |||
| + | there are two possibilties to track this: | ||
| + | |||
| + | 1. Use EIS (eis.services.openoffice.org). Login into EIS, search for the impress110 cws and look there for the modules and files section. There you find the registered task and the files affected by this task. Following the link of the revision shows you the diff. | ||
| + | 2. use bonsai (go-ooo.org/bonsai) to track all the changes of the cws (e.g. http://go-ooo.org/bonsai/cvsquery.cgi?treeid=default&module=all&branch=cws_src680_impress110&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=all&mindate=&maxdate=&cvsroot=%2Fvar%2Fcvsup) | ||
| + | using the first alternative work fine once a cws has been integrated, the second alternative works fine before integration of the cws. | ||
Revision as of 09:19, 7 March 2007
Contents
CVS
This page describes some difficulties with the modified CVS version, which is used for OpenOffice.org
FAQ
I can't checkout with a certain tag
OpenOffice.org CVS is loosing from time to time it's CVSROOT/valtags file so one needs to recreate this tags, this can be done by creating just another dummy branch:
cvs -d:pserver:mh@my-tunnel:/cvs co test cd test/playground cvs tag -b cws_src680_asyncdialogs2 Makefile
how to track the patch code of a issue which has been fixed and integrated ?
(e.g) The issue 69010, belongs to the CWS impress110, has been integrated into m192.
there are two possibilties to track this:
1. Use EIS (eis.services.openoffice.org). Login into EIS, search for the impress110 cws and look there for the modules and files section. There you find the registered task and the files affected by this task. Following the link of the revision shows you the diff. 2. use bonsai (go-ooo.org/bonsai) to track all the changes of the cws (e.g. http://go-ooo.org/bonsai/cvsquery.cgi?treeid=default&module=all&branch=cws_src680_impress110&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=all&mindate=&maxdate=&cvsroot=%2Fvar%2Fcvsup) using the first alternative work fine once a cws has been integrated, the second alternative works fine before integration of the cws.
