Re: Typo in README.barrier
David Rowley <dgrowleyml@gmail.com>
From: David Rowley <dgrowleyml@gmail.com>
To: Tatsuo Ishii <ishii@sraoss.co.jp>
Cc: Michael Paquier <michael@paquier.xyz>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2021-05-17T22:07:30Z
Lists: pgsql-hackers
On Mon, 17 May 2021 at 17:18, Tatsuo Ishii <ishii@sraoss.co.jp> wrote: > > > On Mon, May 17, 2021 at 09:33:27AM +0900, Tatsuo Ishii wrote: > >> Me too. Let's backpatch. > > > > A README is not directly user-facing, it is here for developers, so I > > would not really bother with a backpatch. Now it is not a big deal to > > do so either, so that's not a -1 from me, more a +0, for "please feel > > free to do what you think is most adapted". > > I think README is similar to code comments. If a code comment is > wrong, we usually fix to back branches. Why can't we do the same thing > for README? Thanks for the votes. Since Michael was on the fence and I was just leaning over it and Ishii-san was pro-backpatch, I backpatched it. > > You may want to hold on until 14beta1 is tagged, though. > > Of course we can wait till that day but I wonder why. I imagined that would be a good idea for more risky patches so we don't break something before a good round of buildfarm testing. However, since this is just a README, I didn't think it would have mattered. Maybe there's another reason I'm overlooking? David
Commits
-
Fix typo and outdated information in README.barrier
- 943bda157eca 9.6.23 landed
- e71219ca11fa 10.18 landed
- a399755ba2fc 11.13 landed
- 898c62951e80 12.8 landed
- 010429eb1f77 13.4 landed
- 2ded19fa3a4d 14.0 landed