| From: | Greg Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Aidan Van Dyk <aidan(at)highrise(dot)ca>, Markus Wanner <markus(at)bluegap(dot)ch>, Marko Kreen <markokr(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL Developer meeting minutes up |
| Date: | 2009-06-02 15:19:26 |
| Message-ID: | 4136ffa0906020819t176f34c5g90b3666915025265@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 2, 2009 at 4:02 PM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
>
>
> The Monotone folk call this "daggy fixes" and it seems a clean way to
> handle things.
>
> http://www.monotone.ca/wiki/DaggyFixes/
Is this like what git calls an octopus? I've been wondering what the
point of such things were.
Or maybe not. I thought an octopus was two patches with the same
parent -- ie, two patches that could independently be applied in any
order.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Kreen | 2009-06-02 15:20:32 | Re: PostgreSQL Developer meeting minutes up |
| Previous Message | Markus Wanner | 2009-06-02 15:19:02 | Re: PostgreSQL Developer meeting minutes up |