On Sat, Oct 02 2021, Andrei Rybak wrote: > On the other hand, if you are fetching because you would want a > diff --git a/compat/regex/regcomp.c b/compat/regex/regcomp.c > index d1bc09e49b..fcf7b2daf6 100644 > --- a/compat/regex/regcomp.c > +++ b/compat/regex/regcomp.c > @@ -2370,7 +2370,7 @@ parse_expression (re_string_t *regexp, regex_t *preg, re_token_t *token, > } > /* We must return here, since ANCHORs can't be followed > by repetition operators. > - eg. RE"^*" is invalid or "<ANCHOR(^)><CHAR(*)>", > + e.g. RE"^*" is invalid or "<ANCHOR(^)><CHAR(*)>", > it must not be "<ANCHOR(^)><REPEAT(*)>". */ > fetch_token (token, regexp, syntax); > return tree; Let's leave externally imported code out of these sorts of changes please. The last time I tried (unsuccessfully) to send a series to update compat/regex/ one of the frustrating things was the three-way diff between base/ours/advanced upstream being cluttered by these sorts of tree-wide typo/spelling etc. fixes.
