| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martin Langhoff <martin(at)catalyst(dot)net(dot)nz> |
| Cc: | Aidan Van Dyk <aidan(at)highrise(dot)ca>, "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Hacking on PostgreSQL via GIT |
| Date: | 2007-04-18 05:33:14 |
| Message-ID: | 21068.1176874394@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Martin Langhoff <martin(at)catalyst(dot)net(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martin Langhoff | 2007-04-18 06:39:34 | Re: Hacking on PostgreSQL via GIT |
| Previous Message | Bruce Momjian | 2007-04-18 02:33:21 | Re: Autovacuum vs statement_timeout |