Re: [HACKERS] CVS

From: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
To: "Ansley, Michael" <Michael(dot)Ansley(at)intec(dot)co(dot)za>
Cc: "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] CVS
Date: 1999-07-19 16:58:50
Message-ID: 3793594A.53701A18@alumni.caltech.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Thanks all for this info. I'm presuming that, because no-one has been rude
> yet, that a lot of this is not in the developers manual, or FAQ yet.

Naw, we're just a bunch of polite people, at least today ;)

> Would
> it be worthwhile putting it there? Just a quick paragraph with the latest
> settings, and default options for particular types of developers (e.g.:
> somebody who wants to hack the source and contribute, somebody who wants the
> latest patch tree, somebody who wants access to the latest source, but no
> contributions, etc).

Please look at the appendix entitled "The CVS Repository". The source
is in cvs.sgml (and the derived html or hardcopy appendix is in the
integrated docs or developer's guide). Any and all updates or fixes or
rewrites would be welcome. Also, we should have a good cross-link to
it on the web page if we don't already.

Perhaps current values could go into the FAQ, but the general
principles and today' settings should be in the main docs. So far,
we've had enough docs changes that we get new "big docs" for every
release, though sometime (way in the future) we might have things
settle down and be able to not update them every release.

- Thomas

--
Thomas Lockhart lockhart(at)alumni(dot)caltech(dot)edu
South Pasadena, California

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Carlos Fonseca 1999-07-19 20:23:22 (Debian Bug#41223) cascaded updates with refint insert bogus data
Previous Message Bruce Momjian 1999-07-19 16:45:51 Re: [HACKERS] new patch