Re: Typo in README.barrier

Поиск
Список
Период
Сортировка
От David Rowley
Тема Re: Typo in README.barrier
Дата
Msg-id CAApHDvrcCxv1Y4On-CQL9FmUtCGVWark+C7y6YACoaVR5efjHA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Typo in README.barrier  (Tatsuo Ishii <ishii@sraoss.co.jp>)
Ответы Re: Typo in README.barrier  (Tom Lane <tgl@sss.pgh.pa.us>)
Список 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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: allow specifying direct role membership in pg_hba.conf
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Typo in README.barrier