>>> remerge earthdistance back into pgql-server/contrib and move
>>> pgsql-server to pgsql
>
>> Ugh, this is going to create a *HUGE* headache for many developers.
>
> If you had a problem with it, you should have spoken up earlier when
> it was being discussed.
I missed that discussion (limited bandwidth to read Pg mail, not
reading hackers@ as often as I should). Apologies for the noise, it
just caught me by surprise with all of the conflicts I had this
morning.
>> I think a message to announce@ would be justified with some helpful
>> bits
>> of advice such as the following:
>
> I agree that it needs to be announced, but it would be sufficient to
> tell people to do a fresh checkout. This business of sed'ing changes
> into your CVS/Repository files seems pretty error-prone to me.
It's only as hackish of a way to update a checked out repository as CVS
really is. :) -sc
--
Sean Chittenden
