Re: CVS branch management (was Re: A problem with new pg_dump) - Mailing list pgsql-hackers

From Ian Lance Taylor
Subject Re: CVS branch management (was Re: A problem with new pg_dump)
Date
Msg-id sid79ksjfa.fsf@daffy.airs.com
Whole thread Raw
In response to CVS branch management (was Re: A problem with new pg_dump)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: CVS branch management (was Re: A problem with new pg_dump)  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> writes:

> Unfortunately "cvs log" isn't all that great about distinguishing
> branches from tags --- it calls 'em all "symbolic names".

Minor addition to this: you can distinguish branches and tags by using
`cvs status -v'.

(Historical note: CVS was originally implemented as shell scripts on
top of RCS.  The .0 syntax was magic which CVS used to indicate a
branch as opposed to a revision tag.  The output of `cvs log' is
simply the output of `rlog' on the underlying RCS file.  `cvs status'
is not based on an existing RCS command.)

Ian

---------------------------(end of broadcast)---------------------------
TIP 734: Often statistics are used as a drunken man uses lampposts --
for support rather than illumination.


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: create database name with location = 'path';
Next
From: Vince Vielhaber
Date:
Subject: Re: typo in psql's help