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

From Tom Lane
Subject Re: Hacking on PostgreSQL via GIT
Date
Msg-id 21068.1176874394@sss.pgh.pa.us
Whole thread Raw
In response to Re: Hacking on PostgreSQL via GIT  (Martin Langhoff <martin@catalyst.net.nz>)
Responses Re: Hacking on PostgreSQL via GIT  (Aidan Van Dyk <aidan@highrise.ca>)
Re: Hacking on PostgreSQL via GIT  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: Hacking on PostgreSQL via GIT  (Martin Langhoff <martin@catalyst.net.nz>)
List pgsql-hackers
Martin Langhoff <martin@catalyst.net.nz> writes:
> Aidan Van Dyk wrote:
>> And remember the warning I gave that my conversion is *not* a direct CVS
>> import - I intentionally *unexpand* all Keywords before stuffing them
>> into GIT so that merging and branching can ignore all the Keyword
>> conflicts... 

> My import is unexpanding those as well to support rebasing and merging
> better.

Um ... why do either of you feel there's an issue there?

We switched over to $PostgreSQL$ a few years ago specifically to avoid
creating merge problems for downstream repositories.  If there are any
other keyword expansions left in the source text I'd vote to remove
them.  If you have a problem with $PostgreSQL$, why?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Autovacuum vs statement_timeout
Next
From: Magnus Hagander
Date:
Subject: Re: Autovacuum vs statement_timeout