pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rod Taylor <pg@rbt.ca>
To: Marc G. Fournier <scrappy@postgresql.org>
Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: Hackers <pgsql-hackers@postgresql.org>
Subject: Re: 7.5 Plans
Date: Thu, 27 Nov 2003 00:36:27 -0500
Message-ID: <1069911387.17262.62.camel@jester> (raw)
In-Reply-To: <20031127003125.V41642@ganymede.hub.org>
References: <3FC5610A.40506@familyhealth.com.au>
	<20031126232839.S41642@ganymede.hub.org>
	<1069905941.17262.57.camel@jester>
	<20031127003125.V41642@ganymede.hub.org>

On Wed, 2003-11-26 at 23:32, Marc G. Fournier wrote:
> On Wed, 26 Nov 2003, Rod Taylor wrote:
> 
> > > So, what does changing it to $PostgreSQL$ do?  Or am I reading the wrong
> > > part of the manual?
> >
> > After applying the patch in -patches to CVSROOT and running the update
> > script...
> >
> > It will allow Chris and other to import the PostgreSQL source into their
> > own CVS tree without having do to a ton of diff editing to reimport /
> > export changes between the primary tree and their development tree.
> 
> 'k, but why can't that be accomplished with $Id$?

When you import the files into the other CVS system the version and file
information $Id$ represents will be replaced by the other system. So,
when you diff the original (primary repository) EVERY file will show
$Id$ has changed.

> Are there any caveats to the change?  Ie. if Tom has a checkout and this
> change is made, will he have problems committing?

$VARIABLE$ is used for informational purposes only AFAIK. There would be
no change that I know of.

At work I use $InQuent$, FreeBSD of course uses $FreeBSD$ of which other
BSDs follow suite $NetBSD$ and $OpenBSD$. I've not heard of any issues
with 3rd party CVS clients and any of those repositories in this regard.




view thread (16+ messages)  latest in thread

Message-ID: <1069911387.17262.62.camel@jester>
Permalink:  ../1069911387.17262.62.camel@jester/
Also on:    postgresql.org/message-id/1069911387.17262.62.camel@jester

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: pg@rbt.ca, scrappy@postgresql.org, chriskl@familyhealth.com.au
  Subject: Re: 7.5 Plans
  In-Reply-To: <1069911387.17262.62.camel@jester>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox