Re: CVS corruption/mistagging? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: CVS corruption/mistagging?
Date
Msg-id 23288.1187151191@sss.pgh.pa.us
Whole thread Raw
In response to Re: CVS corruption/mistagging?  ("Marc G. Fournier" <scrappy@hub.org>)
Responses Re: CVS corruption/mistagging?  ("Marc G. Fournier" <scrappy@hub.org>)
List pgsql-hackers
"Marc G. Fournier" <scrappy@hub.org> writes:
> It should be done ... if you try and create a tag, it should generate
> an error message ...

Uh, nope:

$ cvs tag fooey README
T README
$ cvs log README | more

RCS file: /cvsroot/pgsql/src/backend/optimizer/README,v
Working file: README
head: 1.39
branch:
locks: strict
access list:
symbolic names:       fooey: 1.39       REL7_3_19: 1.25       REL7_4_17: 1.29       REL8_0_13: 1.30       REL8_1_9:
1.33      REL8_2_4: 1.35.2.1       REL8_0_12: 1.30       REL8_1_8: 1.33       REL8_2_3: 1.35       REL7_3_18: 1.25
REL7_4_16: 1.29       REL8_0_11: 1.30       REL8_1_7: 1.33       REL8_2_2: 1.35       REL8_0_10: 1.30
 
cvs [log aborted]: received broken pipe signal
$ cvs tag -d fooey README
D README
$ 
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: CVS corruption/mistagging?
Next
From: David Fetter
Date:
Subject: Re: [mmoncure@gmail.com: Re: [GENERAL] array_to_set functions]