Thread: pgsql-server/doc TODO

pgsql-server/doc TODO

From
momjian@svr1.postgresql.org (Bruce Momjian)
Date:
CVSROOT:    /cvsroot
Module name:    pgsql-server
Changes by:    momjian@svr1.postgresql.org    03/06/23 00:52:25

Modified files:
    doc            : TODO

Log message:
    Add:

    > * Change CVS $Id$ to $PostgreSQL$


Re: pgsql-server/doc TODO

From
Sean Chittenden
Date:
> Log message:
>     Add:
>
>     > * Change CVS $Id$ to $PostgreSQL$

<cvsadmin_hat>
This is simple and takes two seconds to do.  The master CVS server has
to be FreeBSD (or have the FreeBSD patches to CVS, which I'm pretty
sure it does if it's running on hub.org):

cd open_source/pgsql/CVSROOT
echo "tag=PostgreSQL=CVSHeader" > options
echo "tagexpand=iPostgreSQL" >> options
echo "options" >> checkoutlist
cvs add options
cvs ci options checkoutlist

The rest is history, nothing else to be done (client or server) but
migrate the $Id$ RCS keywords to $PostgreSQL$.  Wholesale removal of
$Date, $Header, and $Revision$ RCS tags or replacing them with
$PostgreSQL$ would be extremely prudent as they won't be expanded with
the above options file (and the whole point of using $PostgreSQL$ is
to prevent RCS keyword expansion when PostgreSQL's bits are used in
other projects, something that happens with the non-$PostgreSQL$ RCS
keywords in the repos of other projects).  If there's a big stink
about converting everything over, the options file could read like:

echo "tag=PostgreSQL=CVSHeader" > options
echo "tagexpand=iPostgreSQL,Date,Id,Header,Revision" >> options

And at some point in the future (sooner rather than latter,
hopefully), changing the last line of options to be just
"tagexpand=iPostgreSQL".  It might also be worth while to look at
FreeBSD's CVS commit scripts as it collapses the $PostgreSQL$ on disk
thus reducing some diffing and disk space (likely a bigger issue for
FreeBSD than PostgreSQL because of their extensive CVSup mirrors).
They've also got a nifty check in their scripts to make sure that
every file has a $PostgreSQL$ RCS keyword when a commit takes place.
Worth checking out.

Please feel free to ask me Q's if anyone has any Q's about how to do
any of this.
</cvsadmin_hat>

-sc

--
Sean Chittenden

Re: pgsql-server/doc TODO

From
Tom Lane
Date:
Sean Chittenden <sean@chittenden.org> writes:
> They've also got a nifty check in their scripts to make sure that
> every file has a $PostgreSQL$ RCS keyword when a commit takes place.

... that part we definitely do NOT want ...

            regards, tom lane

Re: pgsql-server/doc TODO

From
Rod Taylor
Date:
On Mon, 2003-06-23 at 01:28, Tom Lane wrote:
> Sean Chittenden <sean@chittenden.org> writes:
> > They've also got a nifty check in their scripts to make sure that
> > every file has a $PostgreSQL$ RCS keyword when a commit takes place.
>
> ... that part we definitely do NOT want ...

You can set it up to simply give a warning instead, as well as ignore
certain extensions, etc.

A warning (if it's missing) on the addition of a new file can be a handy
reminder.

--
Rod Taylor <rbt@rbt.ca>

PGP Key: http://www.rbt.ca/rbtpub.asc

Attachment