Re: Tips on committing

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Pg Committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: Tips on committing
Date: 2018-06-28 17:52:42
Message-ID: CAH2-Wz=BkTRfYB9az=G3roKR7d=ob0kDhEkvL8oDPn1XKYDeyg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Thu, Jun 28, 2018 at 9:52 AM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
>> FWIW, I developed a document on committing for my own reference, with
>> some help from Andres.
>
> Sounds very useful.
>
> How about turning it into a wiki page, for everybody's benefit?

I'll try to do that, but I'd still recommend personalizing it. A lot
of the stuff in there is specific to my own workflow and tool
preferences, and my own personal working style. I don't really use a
template in the same way Bruce does, for example, because most of that
stuff is taken care of by my text editor having a "gitcommit" syntax.

I find it useful to have a routine checklist for things like
committing, because it frees up a little space in my head for other
things. I do the same thing when preparing for a trip.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2018-06-29 00:46:31 pgsql: Make capitalization of term "OpenSSL" more consistent
Previous Message Alvaro Herrera 2018-06-28 16:52:14 Re: Tips on committing

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2018-06-28 19:30:01 Re: cost_sort() improvements
Previous Message Andres Freund 2018-06-28 17:06:27 Re: Server crashed with "TRAP: unrecognized TOAST vartag("1", File: "heaptuple.c", Line: 1490)"