Re: Changing "Hot Standby" to "hot standby"
От | Robert Treat |
---|---|
Тема | Re: Changing "Hot Standby" to "hot standby" |
Дата | |
Msg-id | CAJSLCQ0EK6aAyA+76x2x0U+xfz6KSR0UjLtqhKMb1bqyBJeOrg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Changing "Hot Standby" to "hot standby" ("Daniel Westermann (DWE)" <daniel.westermann@dbi-services.com>) |
Ответы |
Re: Changing "Hot Standby" to "hot standby"
|
Список | pgsql-hackers |
On Thu, Mar 10, 2022 at 8:45 AM Daniel Westermann (DWE) <daniel.westermann@dbi-services.com> wrote: > > >>>Hmm. Outside the title that had better use upper-case characters for > >>>the first letter of each word, I can see references to the pattern you > >>>are trying to eliminate in amcheck.sgml (1), config.sgml (3), > >>>protocol.sgml (3) and mvcc.sgml (1). Shouldn't you refresh these as > >>>well if the point is to make the full set of docs consistent? > > >>>As of the full tree, I can see that: > >>> > >>$ git grep "hot standby" | wc -l > >>259 > > >>$ git grep "Hot Standby" | wc -l > >>73 > > >>>So there is a trend for one of the two. > > >>Thanks for looking at it. Yes, I am aware there are other places which would need to be changed and I think I mentionedthat in an >>earlier Email. Are you suggesting to change all at once? I wanted to start with the documentation andthen continue with the other >>places. > > >Attached a new version which also modifies amcheck.sgml, config.sgml, protocol.sgml, and mvcc.sgml accordingly. > > Regards > Daniel > > > From: Daniel Westermann (DWE) <daniel.westermann@dbi-services.com> > Sent: Wednesday, March 9, 2022 15:15 > To: Michael Paquier <michael@paquier.xyz> > Cc: Robert Treat <rob@xzilla.net>; Kyotaro Horiguchi <horikyota.ntt@gmail.com>; aleksander@timescale.com <aleksander@timescale.com>;pgsql-hackers@lists.postgresql.org <pgsql-hackers@lists.postgresql.org> > Subject: Re: Changing "Hot Standby" to "hot standby" > > >>Hmm. Outside the title that had better use upper-case characters for > >>the first letter of each word, I can see references to the pattern you > >>are trying to eliminate in amcheck.sgml (1), config.sgml (3), > >>protocol.sgml (3) and mvcc.sgml (1). Shouldn't you refresh these as > >>well if the point is to make the full set of docs consistent? > > >>As of the full tree, I can see that: > >> > >>$ git grep "hot standby" | wc -l > >>259 > > >>$ git grep "Hot Standby" | wc -l > >>73 > > >>So there is a trend for one of the two. > > >>Thanks for looking at it. Yes, I am aware there are other places which would need to be changed and I think I mentionedthat in an >>earlier Email. Are you suggesting to change all at once? I wanted to start with the documentation andthen continue with the other >>places. > > >Attached a new version which also modifies amcheck.sgml, config.sgml, protocol.sgml, and mvcc.sgml accordingly. > > Sending this again as my last two mails did not seem to reach the archives or the commitfest. Or do they need moderationsomehow? > Not sure why the previous emails didn't go through, and still doesn't look like they were picked up. In the interest of progress though, attaching an updated patch with some minor wordsmithing; lmk if you'd prefer this differently Robert Treat https://xzilla.net
Вложения
В списке pgsql-hackers по дате отправления: