From: | Piotr Stefaniak <postgres(at)piotr-stefaniak(dot)me> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pgindent (was Re: [COMMITTERS] pgsql: Preventive maintenance in advance of pgindent run.) |
Date: | 2017-05-22 05:16:17 |
Message-ID: | VI1PR03MB1199185D2686DB7D7818DBBDF2F80@VI1PR03MB1199.eurprd03.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On 2017-05-22 01:50, Tom Lane wrote:
> Being lazy, I just wiped my copy and re-cloned, but it still seems the
> same as before ... last commit on the pass3 branch is from Mar 4.
> What branch should I be paying attention to?
Sorry for the trouble, this is because I interactively git-rebased it in
order to rewrite history. I do this to limit the number of commits to
the FreeBSD repository. Next time I'll leave fix-ups in chronological
order and meld them with what they fix just before committing to the
FreeBSD repository.
pass3 is the right branch. A fresh clone should have worked as in the
attached log.
Attachment | Content-Type | Size |
---|---|---|
indent-log.txt | text/plain | 3.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2017-05-22 07:10:44 | pgsql: Fix typo in comment |
Previous Message | Tom Lane | 2017-05-21 23:50:14 | Re: pgindent (was Re: [COMMITTERS] pgsql: Preventive maintenance in advance of pgindent run.) |
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro HORIGUCHI | 2017-05-22 05:22:53 | Re: asynchronous execution |
Previous Message | Kyotaro HORIGUCHI | 2017-05-22 04:12:14 | Re: asynchronous execution |