Re: CVS corruption/mistagging?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Kris Jurka <books(at)ejurka(dot)com>, pgsql-hackers(at)postgresql(dot)org, Michael Meskes <meskes(at)postgresql(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net>
Subject: Re: CVS corruption/mistagging?
Date: 2007-08-15 04:13:11
Message-ID: 23288.1187151191@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Marc G. Fournier" <scrappy(at)hub(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2007-08-15 04:15:26 Re: [mmoncure@gmail.com: Re: [GENERAL] array_to_set functions]
Previous Message Tom Lane 2007-08-15 04:08:07 Re: CVS corruption/mistagging?