Issue 31

Summary:	No CVS tag in root of 605 sources
Product:	Build Tools	Reporter:	issues@www <issues>
Component:	code	Assignee:	sander_traveling
Status:	CLOSED NOT_AN_OOO_ISSUE	QA Contact:	issues@www <issues>
Severity:	Trivial
Priority:	P3	CC:	issues
Version:	605
Target Milestone:	---
Hardware:	PC
OS:	All
Issue Type:	DEFECT	Latest Confirmation in:	---
Developer Difficulty:	---

Description issues@www 2000-10-23 04:27:42 UTC

A directory containing CVS information should be in the root directory as well
as the subdirectories, so that one can simply enter `cvs update` to update the
entire tree without setting the CVSROOT and logging in.  A password is always
required the first time one logs in to cvs, of course, but after this the
password would be stored in .cvspass in one's home directory and updating would
be all but automatic.

Comment 1 sander_traveling 2000-10-26 16:09:09 UTC

I'll take it

Comment 2 sander_traveling 2000-10-26 16:17:16 UTC

This is incorrect in case of CVS aliases - as there is no OpenOffice directory
in the CVS repository but only a "virtual" alias, there is no toplevel CVS
directory created. 

This does not keep 'cvs update -r tag' or just 'cvs update' from working.
However, 'cvs update OpenOffice' does not work, but that is behaviour due to cvs
and not something that can be changed in the present setup.

Comment 3 michael.bemmer 2003-03-12 14:22:47 UTC

As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for
details. First step in IssueZilla is unfortunately to set them to verified.

Comment 4 michael.bemmer 2003-03-12 14:23:19 UTC

As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for
details. First step in IssueZilla is unfortunately to set them to verified.

Comment 5 michael.bemmer 2003-03-12 14:23:26 UTC

As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for
details. First step in IssueZilla is unfortunately to set them to verified.

Comment 6 michael.bemmer 2003-03-12 14:40:44 UTC

As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.

Comment 7 michael.bemmer 2003-03-12 14:41:05 UTC

As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.