Difference between revisions of "CVS"
(add basic questions and links) |
({{Bug}}, {{CWS}} templates) |
||
| Line 20: | Line 20: | ||
cvs tag -b cws_src680_asyncdialogs2 Makefile | cvs tag -b cws_src680_asyncdialogs2 Makefile | ||
| − | + | {{Bug|23306}} | |
=== how to track the patch code of a issue which has been fixed and integrated ? === | === 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 | + | (e.g) The issue {{Bug|69010}}, belongs to the {{CWS|impress110}}, has been integrated into {{m|192}}. |
| − | + | There are two possibilties to track this: | |
| − | + | # Use EIS (eis.services.openoffice.org). Login into EIS, search for the <code>impress110</code> 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. | |
| − | + | # use bonsai (go-ooo.org/bonsai) to track all the changes of the cws (e.g. http://bonsai.go-oo.org/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=%2Fhome%2Fooweb%2Fcvsup) | |
| − | + | using the first alternative work fine once a cws has been integrated, the second alternative works fine before integration of the cws. | |
| + | |||
| + | {{LinkBanner}} | ||
Revision as of 10:17, 3 April 2008
This page describes some difficulties with the modified CVS version, which is used for OpenOffice.org
Contents
FAQ
How do I setup a CVS client?
http://specs.openoffice.org/servlets/ProjectSource
How do I setup a tunnel?
http://www.openoffice.org/scdocs/ddSSHGuide
Why do I need a tunnel?
A tunnel is used to commit files to the CVS system. Otherwise you have just read acccess.
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 Issue 69010 , belongs to the CWS impress110 , has been integrated into m192 .
There are two possibilties to track this:
- Use EIS (eis.services.openoffice.org). Login into EIS, search for the
impress110cws 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. - use bonsai (go-ooo.org/bonsai) to track all the changes of the cws (e.g. http://bonsai.go-oo.org/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=%2Fhome%2Fooweb%2Fcvsup)
using the first alternative work fine once a cws has been integrated, the second alternative works fine before integration of the cws.
Tip: On this wiki you can use {{CWS}}, {{m}}, {{Bug}} templates to easily link to child workspaces, milestones and issues.
