Обсуждение: which list?
Which list are the cvs changes posted to? I see that Tom Lane made
changes to just about all of the libpq++ source files but I have no
idea what was done.
Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include <std/disclaimers.h>
TEAM-OS2 Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore
http://www.cloudninegifts.com
==========================================================================
> > Which list are the cvs changes posted to? I see that Tom Lane made > changes to just about all of the libpq++ source files but I have no > idea what was done. Oh, it's a secret. To the committers list, I think. -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania19026
Bruce Momjian <maillist@candle.pha.pa.us> writes:
>> Which list are the cvs changes posted to? I see that Tom Lane made
>> changes to just about all of the libpq++ source files but I have no
>> idea what was done.
> Oh, it's a secret.
> To the committers list, I think.
Right. You can subscribe to either committers or committers-digest
(I use the latter). Also, don't forget that you can use "cvs log"
to examine the log file for any particular file you are concerned
about.
For example:
$ cvs log pgtransdb.cc | more
RCS file: /usr/local/cvsroot/pgsql/src/interfaces/libpq++/pgtransdb.cc,v
Working file: pgtransdb.cc
head: 1.3
branch:
locks: strict
access list:
symbolic names: REL6_4: 1.1.0.2 release-6-3: 1.1
keyword substitution: kv
total revisions: 3; selected revisions: 3
description:
----------------------------
revision 1.3
date: 1999/05/30 15:17:58; author: tgl; state: Exp; lines: +4 -4
Replace static rcsid[] strings by IDENTIFICATION comments in
file headers, to conform to established Postgres coding style and avoid
warnings from gcc.
----------------------------
Or even more directly, use "cvs diff" to see the differences between
any two revisions:
$ cvs diff -c -r 1.4 -r 1.5 pglobject.cc
Index: pglobject.cc
===================================================================
RCS file: /usr/local/cvsroot/pgsql/src/interfaces/libpq++/pglobject.cc,v
retrieving revision 1.4
retrieving revision 1.5
diff -c -r1.4 -r1.5
*** pglobject.cc 1999/05/23 01:04:03 1.4
--- pglobject.cc 1999/05/30 15:17:58 1.5
***************
*** 9,14 ****
--- 9,16 ---- * * Copyright (c) 1994, Regents of the University of California *
+ * IDENTIFICATION
+ * $Header: /usr/local/cvsroot/pgsql/src/interfaces/libpq++/pglobject.cc,v 1.5 1999/05/30 15:17:58 tgl Exp $ *
*------------------------------------------------------------------------- */
***************
*** 18,25 **** } #include "pglobject.h"
-
- static char rcsid[] = "$Id: pglobject.cc,v 1.4 1999/05/23 01:04:03 momjian Exp $"; //
****************************************************************//
--- 20,25 ----
See the cvs manual for these and many more useful features...
regards, tom lane
On 01-Jun-99 Tom Lane wrote:
> Bruce Momjian <maillist@candle.pha.pa.us> writes:
>>> Which list are the cvs changes posted to? I see that Tom Lane made
>>> changes to just about all of the libpq++ source files but I have no
>>> idea what was done.
>
>> Oh, it's a secret.
>> To the committers list, I think.
>
> Right. You can subscribe to either committers or committers-digest
> (I use the latter). Also, don't forget that you can use "cvs log"
> to examine the log file for any particular file you are concerned
> about.
>
> For example:
>
> $ cvs log pgtransdb.cc | more
Using cvsup that doesn't work very well. I'll have to configure cvs to
look at hub. From hub I apparently aren't configured/not allowed to see
that part of the tree.
Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include <std/disclaimers.h>
TEAM-OS2 Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore
http://www.cloudninegifts.com
==========================================================================
On 01-Jun-99 Vince Vielhaber wrote: > > On 01-Jun-99 Tom Lane wrote: >> Bruce Momjian <maillist@candle.pha.pa.us> writes: >>>> Which list are the cvs changes posted to? I see that Tom Lane made >>>> changes to just about all of the libpq++ source files but I have no >>>> idea what was done. >> >>> Oh, it's a secret. >>> To the committers list, I think. >> >> Right. You can subscribe to either committers or committers-digest >> (I use the latter). Also, don't forget that you can use "cvs log" >> to examine the log file for any particular file you are concerned >> about. >> >> For example: >> >> $ cvs log pgtransdb.cc | more > > Using cvsup that doesn't work very well. I'll have to configure cvs to > look at hub. From hub I apparently aren't configured/not allowed to see > that part of the tree. Responding to my own post (it's ok as long as I don't argue with myself :) While trying to catch upon a few older items, I got to a little thing that Hal sent me a couple weeks ago and solves that dilemna. http://www.postgresql.org/cgi/cvswebtest.cgi Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include <std/disclaimers.h> TEAM-OS2 Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore http://www.cloudninegifts.com ==========================================================================
You should have access to the complete pgsql source tree from hub...do you get an error if you try? On Mon, 31 May 1999, Vince Vielhaber wrote: > > On 01-Jun-99 Tom Lane wrote: > > Bruce Momjian <maillist@candle.pha.pa.us> writes: > >>> Which list are the cvs changes posted to? I see that Tom Lane made > >>> changes to just about all of the libpq++ source files but I have no > >>> idea what was done. > > > >> Oh, it's a secret. > >> To the committers list, I think. > > > > Right. You can subscribe to either committers or committers-digest > > (I use the latter). Also, don't forget that you can use "cvs log" > > to examine the log file for any particular file you are concerned > > about. > > > > For example: > > > > $ cvs log pgtransdb.cc | more > > Using cvsup that doesn't work very well. I'll have to configure cvs to > look at hub. From hub I apparently aren't configured/not allowed to see > that part of the tree. > > Vince. > -- > ========================================================================== > Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null > # include <std/disclaimers.h> TEAM-OS2 > Online Campground Directory http://www.camping-usa.com > Online Giftshop Superstore http://www.cloudninegifts.com > ========================================================================== > > > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
Vince Vielhaber <vev@michvhf.com> writes:
>> For example:
>> $ cvs log pgtransdb.cc | more
> Using cvsup that doesn't work very well.
Hmm ... I've got to think you've got cvsup misconfigured somehow.
It works great for me with a plain cvs setup. cvs log and similar
operations have to contact hub.org to work, but that's no big
problem for me. I believe the advantage of cvsup is that you have
all the same info stored locally, which is cool if you don't mind
expending the disk space. So it *should* Just Work.
If there's some critical bit of configuration info that's missing
from the new Postgres docs about CVS (doc/src/sgml/cvs.sgml),
please let Thomas know when you figure it out...
regards, tom lane
> > Also, don't forget that you can use "cvs log"
> > to examine the log file for any particular file
> > you are concerned about.
> > For example:
> > $ cvs log pgtransdb.cc | more
> Using cvsup that doesn't work very well.
Just a reminder: imho it makes no sense to run cvsup in any mode other
than fetching the entire cvs repository. Then you can do any and all
cvs reading operations locally. The new cvs docs show an example which
does this, but the sample cvsup configuration file posted at
postgresql.org still only shows the "fetch current checkout tree"
example which is far less useful.
- Thomas
--
Thomas Lockhart lockhart@alumni.caltech.edu
South Pasadena, California
Thomas Lockhart <lockhart@alumni.caltech.edu> writes:
> Just a reminder: imho it makes no sense to run cvsup in any mode other
> than fetching the entire cvs repository. Then you can do any and all
> cvs reading operations locally. The new cvs docs show an example which
> does this, but the sample cvsup configuration file posted at
> postgresql.org still only shows the "fetch current checkout tree"
> example which is far less useful.
Right ... if you want to store only the current tree locally, you might
as well forget cvsup and just use bare cvs.
regards, tom lane
On Tue, 1 Jun 1999, Thomas Lockhart wrote:
> > > Also, don't forget that you can use "cvs log"
> > > to examine the log file for any particular file
> > > you are concerned about.
> > > For example:
> > > $ cvs log pgtransdb.cc | more
> > Using cvsup that doesn't work very well.
>
> Just a reminder: imho it makes no sense to run cvsup in any mode other
> than fetching the entire cvs repository. Then you can do any and all
> cvs reading operations locally. The new cvs docs show an example which
> does this, but the sample cvsup configuration file posted at
> postgresql.org still only shows the "fetch current checkout tree"
> example which is far less useful.
Yep, I read your FAQ this mourning and made some changes to my cvsup
file to get the entire tree. Had I done that sooner I'd have saved
myself some extra work when I wiped out an sgml file I'd been working
on! Tonite I should be set up the rest of the way.
Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include <std/disclaimers.h>
TEAM-OS2 Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore
http://www.cloudninegifts.com
==========================================================================