Re: TODO: Rename some /contrib modules from pg* to pg_*

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
Cc: scrappy(at)postgresql(dot)org, jd(at)commandprompt(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: TODO: Rename some /contrib modules from pg* to pg_*
Date: 2006-06-08 23:36:52
Message-ID: 3413.1149809812@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Andrew Dunstan" <andrew(at)dunslane(dot)net> writes:
> Renaming directories is nasty in CVS no matter which way you look at it - it
> is one of the known bad limitations. You might preserve the history but you
> could also break every existing repo copy. See
> http://ximbiot.com/cvs/manual/cvs-1.11.15/cvs_7.html#SEC74

> Unless there is a *very* good reason this should be avoided.

I think the we-shouldn't-rename-the-shlibs argument is sufficient to
kill the idea, quite aside from CVS limitations.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2006-06-08 23:39:51 Re: TODO: Determine optimal fdatasync/fsync, O_SYNC/O_DSYNC options
Previous Message Marc G. Fournier 2006-06-08 23:10:28 Re: TODO: Rename some /contrib modules from pg* to pg_*