Re: bulk typos
Justin Pryzby <pryzby@telsasoft.com>
From: Justin Pryzby <pryzby@telsasoft.com>
To: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Cc: Heikki Linnakangas <heikki.linnakangas@iki.fi>, Surafel Temesgen <surafel3000@gmail.com>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Pavel Stehule <pavel.stehule@gmail.com>, Julien Rouhaud <rjuju123@gmail.com>
Date: 2020-10-31T02:08:01Z
Lists: pgsql-hackers
Attachments
- 0001-pgindent-typos.patch (text/x-diff)
On Sun, Oct 25, 2020 at 02:48:49PM -0500, Justin Pryzby wrote: > On Sat, Mar 31, 2018 at 05:56:40AM -0500, Justin Pryzby wrote: > > I needed another distraction so bulk-checked for typos, limited to comments in > > *.[ch]. > > > > I'm not passionate about this, but it serves the purpose of reducing the > > overhead of fixing them individually. > > I happened across this old patch, so ran this again to find new typos. > > There's a few that I don't know how best to fix. I've added a few more, but still not sure about these two. > Pavel, I can't understand this one. > I guess s/producement/producing/ is too simple of a fix. > Please check my proposed language. > +XmlTableFetchRow(TableFuncScanState *state) > + * XmlTable returns table - set of composite values. The error context, is > + * used for producement more values, between two calls, there can be > + * created and used another libxml2 error context. ... > > Surafel, this typo existed twice in the original commit (357889eb1). > One instance was removed by Tom in 35cb574aa. Should we simply fix the typo, > or borrow Julien/Tom's lanuage? > + * Tuple at limit is needed for comparation in subsequent > + * execution to detect ties.
Commits
-
Fix some grammar and typos in comments and docs
- c6671cdbde93 9.6.20 landed
- b99cbbf5ce51 10.15 landed
- c7f41b2999c3 11.10 landed
- bebad3342004 12.5 landed
- 796885a07133 13.1 landed
- 8a15e735be00 14.0 landed
-
Fix a boatload of typos in C comments.
- 0b11a674fb11 11.0 landed