Re: CVS branch management (was Re: A problem with new pg_dump)

From: Ian Lance Taylor <ian(at)airs(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Philip Warner <pjw(at)rhyme(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: CVS branch management (was Re: A problem with new pg_dump)
Date: 2001-05-08 01:45:13
Message-ID: sid79ksjfa.fsf@daffy.airs.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Vince Vielhaber 2001-05-08 01:46:40 Re: typo in psql's help
Previous Message Tom Lane 2001-05-08 01:42:04 Re: create database name with location = 'path';