From: | Vince Vielhaber <vev(at)michvhf(dot)com> |
---|---|
To: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] which list? |
Date: | 1999-06-01 16:26:57 |
Message-ID: | Pine.BSF.4.05.9906011224460.22684-100000@paprika.michvhf.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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(at)michvhf(dot)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
==========================================================================
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1999-06-01 16:30:59 | Re: [HACKERS] LIMITS |
Previous Message | Tom Lane | 1999-06-01 16:23:30 | Re: [HACKERS] which list? |