Re: Hacking on PostgreSQL via GIT - Mailing list pgsql-hackers

From Aidan Van Dyk
Subject Re: Hacking on PostgreSQL via GIT
Date
Msg-id 20070418185954.GZ5066@yugib.highrise.ca
Whole thread Raw
In response to Re: Hacking on PostgreSQL via GIT  ("Jim C. Nasby" <jim@nasby.net>)
Responses Re: Hacking on PostgreSQL via GIT  (Aidan Van Dyk <aidan@highrise.ca>)
List pgsql-hackers
* Jim C. Nasby <jim@nasby.net> [070418 14:39]:
> On Wed, Apr 18, 2007 at 06:39:34PM +1200, Martin Langhoff wrote:
> > Keyword expansions are generally bad because SCM tools should track
> > _content_ - and keyword expansions _modify_ it to add metadata that is
> > somewhat redundant, obtainable in other ways, and should just not be in
> > the middle of the _data_. Those modifications lead to patches that have
> > bogus hunks and sometimes don't apply, MD5/SHA1 checksums that don't
> > match and a whole lot of uncertainty.
> 
> Then how do you tell what version a file is if it's outside of a
> checkout?

That's what all the fun is about ;-)  Some would say that "labelling" the
file is the job of the release processes.  Others say it's the job of
the SCM system...

Of course I just sit on the fence because in the work I have to do, I'm
quite happy that nothing is "outside of a checkout".  GIT is good enough
that I have it everywhere.  I realise not everyone's that lucky..

;-)

a.

-- 
Aidan Van Dyk                                             Create like a god,
aidan@highrise.ca                                       command like a king,
http://www.highrise.ca/                                   work like a slave.

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [RFC] PostgreSQL Access Control Extension (PGACE)
Next
From: Aidan Van Dyk
Date:
Subject: Re: Hacking on PostgreSQL via GIT