| From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | Vince Vielhaber <vev(at)michvhf(dot)com> |
| 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:22:54 |
| Message-ID: | 375408DE.D9F9ACAF@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > 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(at)alumni(dot)caltech(dot)edu
South Pasadena, California
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 1999-06-01 16:23:30 | Re: [HACKERS] which list? |
| Previous Message | Pablo Funes | 1999-06-01 16:09:36 | Re: [HACKERS] please? |