Skip site navigation (1) Skip section navigation (2)

Re: Odd CVS revision number

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>,PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Odd CVS revision number
Date: 2010-02-25 15:49:52
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Andrew Dunstan wrote:

> For some unknown reason, we have some version 2.x files in
> doc/src/sgml:
> <>,
> which is why
> you saw this.

Most likely, somebody incremented the rev number by hand in the dawn of
time.  Your doc also says:

	It's easy to tell CVS to increment the first digit of the
	revision number, provided that you're setting it to something
	equal to or greater than the highest first digit of all
	revisions of all files in the same directory. Just use the -r
	flag on commit. For example:

	    cvs commit -r 2 <file>

	where <file> currently has a revision of 1.<something>, will
	check in that file with a new revision of 2.1.

Alvaro Herrera                      
The PostgreSQL Company - Command Prompt, Inc.

In response to

pgsql-hackers by date

Next:From: Dominik SanderDate: 2010-02-25 15:52:32
Subject: Boolean partition constraint behaving strangely
Previous:From: Fujii MasaoDate: 2010-02-25 15:45:41
Subject: Re: Streaming replication and pg_xlogfile_name()

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group