| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Aidan Van Dyk <aidan(at)highrise(dot)ca> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Markus Wanner <markus(at)bluegap(dot)ch>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL Developer meeting minutes up |
| Date: | 2009-05-28 02:42:46 |
| Message-ID: | 603c8f070905271942ke9df2aah8648fe4d1228d43e@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 27, 2009 at 10:09 PM, Aidan Van Dyk <aidan(at)highrise(dot)ca> wrote:
> * Robert Haas <robertmhaas(at)gmail(dot)com> [090527 21:30]:
>
>> > And actually looking at the history of the gpo repo, the branches are all
>> > messed up with "merges" and stuff that I'm not sure where they are coming
>> > from... 8.2, 8.3, and master(HEAD) are all the same as my gpo repo, but the
>> > back branchs are very bad...
>>
>> This is really quite horrible. What is the best way forward here?
>
> That depends entirely on what the project wants.
I can't speak for anyone else, but what I want is for the git tree on
git.postgresql.org to match CVS.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-05-28 03:14:45 | Re: search_path vs extensions |
| Previous Message | Robert Haas | 2009-05-28 02:41:06 | Re: User-facing aspects of serializable transactions |