Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2])
	by hub.org (8.9.3/8.9.3) with ESMTP id JAA98215
	for <pgsql-hackers@postgreSQL.org>;
	Tue, 14 Sep 1999 09:54:37 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id JAA15998;
	Tue, 14 Sep 1999 09:53:52 -0400 (EDT)
To: Bruce Momjian <maillist@candle.pha.pa.us>
cc: "pgsql-hackers@postgreSQL.org" <pgsql-hackers@postgreSQL.org>
Subject: Re: [HACKERS] Re: HISTORY for 6.5.2 
In-reply-to: Your message of Mon, 13 Sep 1999 21:03:04 -0400 (EDT)
	<199909140103.VAA06678@candle.pha.pa.us>
Date: Tue, 14 Sep 1999 09:53:52 -0400
Message-ID: <15996.937317232@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Bruce Momjian <maillist@candle.pha.pa.us> writes:
>> This is *not* in 6.5.*, only 6.6.

> I have:
> 	RCS file: /usr/local/cvsroot/pgsql/src/interfaces/libpq/pqexpbuffer.c,v
> 	Working file: src/interfaces/libpq/pqexpbuffer.c
> 	head: 1.1

> Seems addition of text files shows up in all branches, which I guess
> makes sense.  No cause for alarm.

I've noticed that cvs log seems a little bogus in its handling of
branches, even though cvs status and cvs update know perfectly well
what belongs to the local branch and what doesn't.  If you say
"cvs log" you get the "current" (tip revision's) log entries, even
if you are in a directory that's been checked out with a sticky
branch tag.  If you say "cvs log -rBRANCH" you get the branch's
log entries, but *only* those applied since the branch was split;
there doesn't seem to be any way to get the full history as seen
in this branch.  And, as above, it's quite confusing about files
that are not in the local branch at all.

Dunno if the cvs folk consider these behaviors bugs or features,
but they're definitely something to be wary of when working in
a branch...

			regards, tom lane