On 2022-Aug-05, Alvaro Herrera wrote:
> On 2022-Aug-05, Andrew Dunstan wrote:
>
> > let's just backpatch the file and be done with it.
>
> I can do that in a couple of hours.
Done.
Thanks!
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"La rebeldía es la vir
On 2022-Aug-05, Andrew Dunstan wrote:
> let's just backpatch the file and be done with it.
I can do that in a couple of hours.
--
Álvaro HerreraBreisgau, Deutschland — https://www.EnterpriseDB.com/
"You don't solve a bad join with SELECT DISTINCT" #CupsOfFail
https://twitter.com/conno
On 2022-08-04 Th 20:35, Peter Geoghegan wrote:
> On Mon, Jul 11, 2022 at 12:30 PM Alvaro Herrera
> wrote:
>> $ git blame configure
>> fatal: could not open object name list: .git-blame-ignore-revs
>>
>> My first workaround was to add empty .git-blame-ignore-revs in all
>> checkouts. This was m
On Mon, Jul 11, 2022 at 12:30 PM Alvaro Herrera wrote:
> $ git blame configure
> fatal: could not open object name list: .git-blame-ignore-revs
>
> My first workaround was to add empty .git-blame-ignore-revs in all
> checkouts. This was moderately ok (shrug), until after a recent `tig`
> upgrade
On Mon, Jul 11, 2022 at 12:36 PM Tom Lane wrote:
> Only if we had to update all those copies all the time. But
> I'm guessing we wouldn't need a branch's copy to be newer than
> the last pgindent run affecting that branch?
I wouldn't care very much if the file itself was empty in the
backbranche
> On 11 Jul 2022, at 21:35, Tom Lane wrote:
>
> Alvaro Herrera writes:
>> A viable option would be to backpatch the addition of
>> .git-blame-ignore-revs to all live branches. Would that bother anyone?
>
> Only if we had to update all those copies all the time. But
> I'm guessing we wouldn't
On Mon, Jul 11, 2022 at 12:30 PM Alvaro Herrera wrote:
> Anybody has any idea how to handle this better?
>
> A viable option would be to backpatch the addition of
> .git-blame-ignore-revs to all live branches. Would that bother anyone?
+1. I was thinking of suggesting the same thing myself, for
Alvaro Herrera writes:
> A viable option would be to backpatch the addition of
> .git-blame-ignore-revs to all live branches. Would that bother anyone?
Only if we had to update all those copies all the time. But
I'm guessing we wouldn't need a branch's copy to be newer than
the last pgindent ru
> On 11 Jul 2022, at 18:31, Alvaro Herrera wrote:
> A viable option would be to backpatch the addition of
> .git-blame-ignore-revs to all live branches. Would that bother anyone?
I wouldn't mind having it backpatched.
--
Daniel Gustafsson https://vmware.com/
I like the ignore-revs file, but I run into a problem with my setup:
because I keep checkouts of all branches as worktrees, then all branches
share the same .git/config file. So if I put the recommended stanza for
[blame] in it, then 'git blame' complains in branches older than 13,
since those don
10 matches
Mail list logo
