Skip site navigation (1) Skip section navigation (2)

Re: Several tags around PostgreSQL 7.1 broken

From: Aidan Van Dyk <aidan(at)highrise(dot)ca>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Several tags around PostgreSQL 7.1 broken
Date: 2008-04-01 18:20:39
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
* Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> [080401 14:15]:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > In the meantime, does anyone have more information about how this came about?
> Marc's always done both the tagging and the tarball-making, so you'd
> have to ask him about that.  I believe he's made it more scripted over
> the years, so this might reflect a manual foulup that (hopefully) is no
> longer possible.
> +1 for adjusting the tags in CVS to match what we actually shipped.
> 			regards, tom lane

If somebody's going to be fudging around in $CVSROOT, is it possible to
give us all a big warning, and hopefully "pause" the anoncvs/rsync sync
stuff for the duration of the "history change", so we (those of us out
here working off anoncvs/rsync) get an atomic swap of ancient history?

Aidan Van Dyk                                             Create like a god,
aidan(at)highrise(dot)ca                                       command like a king,                                   work like a slave.

In response to

pgsql-hackers by date

Next:From: Paul RamseyDate: 2008-04-01 18:37:40
Subject: Access to Row ID information in Functions
Previous:From: Tom LaneDate: 2008-04-01 18:06:09
Subject: Re: Several tags around PostgreSQL 7.1 broken

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group