Re: Maintaining a list of pgindent commits for "git blame" to ignore

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Maintaining a list of pgindent commits for "git blame" to ignore
Date: 2021-03-20 02:33:21
Message-ID: CAH2-Wz=9-3Y2KtVd5CjsetJEq3Mn9919afDjVOXyd+qXbtDktA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 18, 2021 at 5:07 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Doubt that it matters. The workflow would have to be "commit and push
> the mechanical updates, then edit the tracking file, commit and push
> that". You don't have the commit hash nailed down till you've pushed.

Okay. I have made a personal TODO list item for this. I'll pick this
up again in April, once the final CF is over.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2021-03-20 02:35:29 recovery_init_sync_method=wal
Previous Message Amit Kapila 2021-03-20 02:21:26 Re: [HACKERS] logical decoding of two-phase transactions