| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: a raft of parallelism-related bug fixes |
| Date: | 2016-02-08 22:39:03 |
| Message-ID: | CAM3SWZR=DwhLozHwve54C7aHVvH5Cnxe5JtV7W5tXWXEOQQcCA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Feb 8, 2016 at 2:35 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> I think having a public git tree, that contains the current state, is
> greatly helpful for that. Just announce that you're going to screw
> wildly with history, and that you're not going to be terribly careful
> about commit messages. That means observers can just do a fetch and a
> reset --hard to see the absolutely latest and greatest. By all means
> post a series to the list every now and then, but I think for minor
> changes it's perfectly sane to say 'pull to see the fixups for the
> issues you noticed'.
I would really like for there to be a way to do that more often. It
would be a significant time saver, because it removes problems with
minor bitrot.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2016-02-08 22:45:01 | Re: 2016-01 Commitfest |
| Previous Message | Andres Freund | 2016-02-08 22:35:38 | Re: a raft of parallelism-related bug fixes |