Re: $PostgreSQL$ for revision info - Mailing list pgsql-hackers

From Sean Chittenden
Subject Re: $PostgreSQL$ for revision info
Date
Msg-id 20030523010538.GM71079@perrin.int.nxad.com
Whole thread Raw
In response to Re: $PostgreSQL$ for revision info  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: $PostgreSQL$ for revision info
List pgsql-hackers
> > Would anyone object to replacing $Header$ and $Id$ with $PostgreSQL$ for
> > a file version marker?
> 
> I don't really care to depend on a nonstandard CVS setup...

Data point: Most large projects that have their source routinely
imported into other repositories or import other bits of code, make
heavy use of non-standard $Id$'s for the sake of reducing diff's and
collisions.  The BSDs are the biggest examples and users of this.  I
personally would very much like to see this change as I've grumbled
about doing imports of PostgreSQL into repos that I don't manage and
having lost version information because of colliding $Id$ tags.

Using the options file is pretty standard and has a long history of
use.

http://www.freebsd.org/cgi/cvsweb.cgi/CVSROOT/options

-sc

-- 
Sean Chittenden


pgsql-hackers by date:

Previous
From: Kurt Roeckx
Date:
Subject: Password authentication confusion.
Next
From: "Christopher Kings-Lynne"
Date:
Subject: Un-clustering an index