..............................................................................1337 F. The CVS Repository............................................................................................... their own copies of the PostgreSQL CVS repository. File version stamps from the master repository will not get munged by checking into or out of a copied repository. 1221 Appendix E. Release Notes • Clarify date: 1995-05-01 1337 Appendix E. Release Notes Initial release. 1338 Appendix F. The CVS Repository Marc Fournier, Tom Lane, and Thomas Lockhart1999-05-20 The PostgreSQL source code is stored and

..............................................................................1251 F. The CVS Repository............................................................................................... their own copies of the PostgreSQL CVS repository. File version stamps from the master repository will not get munged by checking into or out of a copied repository. • Clarify locking code (Manfred Koizar) Postgres95 Release 0.01 Release date: 1995-05-01 Initial release. 1252 Appendix F. The CVS Repository Marc Fournier, Tom Lane, and Thomas Lockhart1999-05-20 The PostgreSQL source code is stored and

..............................................................................1509 F. The CVS Repository............................................................................................... their own copies of the PostgreSQL CVS repository. File version stamps from the master repository will not get munged by checking into or out of a copied repository. • Clarify locking code (Manfred Koizar) Postgres95 Release 0.01 Release date: 1995-05-01 Initial release. 1509 Appendix F. The CVS Repository The PostgreSQL source code is stored and managed using the CVS code management system. At least

..............................................................................1461 F. The CVS Repository............................................................................................... their own copies of the PostgreSQL CVS repository. File version stamps from the master repository will not get munged by checking into or out of a copied repository. • Clarify locking code (Manfred Koizar) Postgres95 Release 0.01 Release date: 1995-05-01 Initial release. 1461 Appendix F. The CVS Repository The PostgreSQL source code is stored and managed using the CVS code management system. At least

..............................................................................1655 F. The CVS Repository............................................................................................... their own copies of the PostgreSQL CVS repository. File version stamps from the master repository will not get munged by checking into or out of a copied repository. • Clarify locking code (Manfred Koizar) Postgres95 Release 0.01 Release date: 1995-05-01 Initial release. 1655 Appendix F. The CVS Repository The PostgreSQL source code is stored and managed using the CVS version control system. At least

......................................................................1690 F. The Source Code Repository .............................................................................................. command by hand, instead. • Update build infrastructure and documentation to reflect the source code repository’s move from CVS to Git (Magnus Hagander and others) • Update time zone data files to tzdata release (Itagaki Takahiro) • Update build infrastructure and documentation to reflect the source code repository’s move from CVS to Git (Magnus Hagander and others) • Update time zone data files to tzdata release

......................................................................2043 H. The Source Code Repository .............................................................................................. command by hand, instead. • Update build infrastructure and documentation to reflect the source code repository’s move from CVS to Git (Magnus Hagander and others) • Update time zone data files to tzdata release command by hand, instead. • Update build infrastructure and documentation to reflect the source code repository’s move from CVS to Git (Magnus Hagander and others) • Update time zone data files to tzdata release

......................................................................1922 H. The Source Code Repository ...........................................................................................1923 command by hand, instead. • Update build infrastructure and documentation to reflect the source code repository’s move from CVS to Git (Magnus Hagander and others) • Update time zone data files to tzdata release command by hand, instead. • Update build infrastructure and documentation to reflect the source code repository’s move from CVS to Git (Magnus Hagander and others) • Update time zone data files to tzdata release

......................................................................2125 H. The Source Code Repository ...........................................................................................2127 rest of the installation procedure. You can also get the source directly from the version control repository, see Appendix H. 15.4. Upgrading These instructions assume that your existing installation is command by hand, instead. • Update build infrastructure and documentation to reflect the source code repository’s move from CVS to Git (Magnus Hagander and others) • Update time zone data files to tzdata release

......................................................................2265 H. The Source Code Repository .............................................................................................. rest of the installation procedure. You can also get the source directly from the version control repository, see Appendix H. 357 Chapter 15. Installation from Source Code 15.4. Upgrading These instructions command by hand, instead. • Update build infrastructure and documentation to reflect the source code repository’s move from CVS to Git (Magnus Hagander and others) • Update time zone data files to tzdata release