Issue 8870 - Correct branch tag on OOO_STABLE_1
Summary: Correct branch tag on OOO_STABLE_1
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: _openoffice.org CVS (obsolete) (show other issues)
Version: current
Hardware: PC All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: Martin Hollmichel
QA Contact: issues@www
URL:
Keywords:
: 8871 (view as issue list)
Depends on:
Blocks:
 
Reported: 2002-10-31 16:34 UTC by mmeeks
Modified: 2004-02-17 09:03 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description mmeeks 2002-10-31 16:34:54 UTC 
So; it seems that the date / branch information is not getting synched correctly
to anoncvs.openoffice.org.

To demonstrate this; simply checkout a branch; eg. OOO_STABLE_1; cd solver/inc
and compare this:

cvs -d ':pserver:anoncvs@anoncvs.openoffice.org:/cvs' upd -r OOO_STABLE_1
tg_ext.mk ; cvs -d ':pserver:anoncvs@anoncvs.openoffice.org:/cvs' upd -r
OOO_STABLE_1 -D '1 second ago' tg_ext.mk
U tg_ext.mk
cvs server: tg_ext.mk is no longer in the repository

it seemed that this did work from ftp.stardiv.de's anoncvs, but perhaps that was
a different issue.
Comment 1 stx123 2002-10-31 17:45:59 UTC 
Martin, is that the issue, you discussed with Michael?
Seems, you can use his command to detect the malicious files.
Comment 2 Martin Hollmichel 2002-10-31 18:22:14 UTC 
yes, it is. fixed now for this file. I think we'll have tomorrorw
result for the other files.
Comment 3 Martin Hollmichel 2002-10-31 18:24:01 UTC 
*** Issue 8871 has been marked as a duplicate of this issue. ***
Comment 4 stx123 2002-10-31 18:25:07 UTC 
Let's use this bug to track the erroneous file.
Comment 5 stx123 2002-11-01 14:13:00 UTC 
Michael found some more files not tagged as branch...
Comment 6 mmeeks 2002-11-04 10:35:32 UTC 
Everything is working fine for me now; at least on OOO_STABLE_1; it
remains to be seen how SRX643_OO will cope with -D '0 seconds ago' ;-)
Comment 7 Martin Hollmichel 2004-02-17 09:00:41 UTC 
verified.
Comment 8 Martin Hollmichel 2004-02-17 09:03:07 UTC 
close issue.