| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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>, Marc Fournier <scrappy(at)hub(dot)org> |
| Subject: | Re: CVS corruption/mistagging? |
| Date: | 2007-08-15 06:02:28 |
| Message-ID: | 46C296F4.5070806@hagander.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> So I'd say your strategy looks good - backup and remove the phony tag.
>> I'd also say we should probably be logging tag commands in taginfo.
>> Presumably we mere mortal committers should not be doing any tagging
>> whatsoever, and tags should only be applied in preparation for releases.
>
> +1 ... we should at least log such commands, and maybe disallow to anyone
> except Marc's "pgsql" account. Particularly since they don't get
> reported in pgsql-committers messages (or is that something we
> can/should change?)
>
I think you can, by sticking a command in the taginfo command. It's the
same script that Marc is using to try to restrict who can do it - once
he has that working, it should be as simple as adding a mail command to
the end of that script.
And +1 on doing it.
//Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2007-08-15 06:10:47 | Re: tsearch2 in PostgreSQL 8.3? |
| Previous Message | Pavel Stehule | 2007-08-15 06:01:24 | is this trigger safe and efective? - locking (caching via triiggers) |