| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql: some bullshit |
| Date: | 2015-12-22 07:55:50 |
| Message-ID: | CAB7nPqSdPKqN9qHNUb_pWbnORfMkDHuv_8WvOVzFeYCY7F19cA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On Tue, Dec 22, 2015 at 8:16 AM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Alvaro Herrera wrote:
>> some bullshit
>
> This commit was supposed to be squashed with the next one --- hence
> the, err, not-terribly-descriptive commit message. This mistake may
> cause future "git bisect" runs to give spurious failures, but I'm
> disinclined to remove it from history nonetheless. These changes (which
> would cause a compile to fail on this branch) are removed by the next
> commit.
That's not the first time something that breaks compilation of the
backend has been committed, and among all the things that already
happened nobody yet complained about a bisect failing. So no worries
regarding that and take it easy :)
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2015-12-22 10:57:52 | Re: pgsql: some bullshit |
| Previous Message | Robert Haas | 2015-12-22 05:06:58 | Re: pgsql: some bullshit |