bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Spelling fixes for gnulib


From: Josh Soref
Subject: Re: Spelling fixes for gnulib
Date: Fri, 9 Jun 2023 00:09:48 -0400

Paul Eggert <eggert@cs.ucla.edu> wrote:
> Thanks, I installed most of them, though with some changes as some fixes
> need to be installed upstream first,

I saw you send one to texinfo.

I think these are the ones that were reverted by some automatic things
from other upstreams:
https://github.com/jsoref/gnu-gnulib/commit/142ff39f17f846808d018a1eb5e43d5e9ee7d2e6

Will someone else manage pulling in those bits? Or am I responsible for that?

> and others didn't seem to be needed
> ("obsolescent" is a word and has a different meaning from "obsolete").

I'm aware they're distinct words, but I believe that `obsolete` is the
appropriate term.

obsolescent is about "becoming obsolete", but afaict all of the
instances involve cases where something has declared a thing as in
fact *being* obsolete as opposed to merely things which through (lack
of) common usage are becoming obsolete.

> Plus I fixed some nearby grammar issues.

The additional "in the neighborhood" changes look great.

> Attached is what I installed.

Thanks, I pulled in the changes as
https://github.com/jsoref/gnu-gnulib/commits/142ff39f17f846808d018a1eb5e43d5e9ee7d2e6

For the curious, these are the bits which weren't dropped when I rebased:
https://github.com/jsoref/gnu-gnulib/compare/142ff39f17f846808d018a1eb5e43d5e9ee7d2e6...ab197e8f81389c3c2d27c8ebd5f9af0c516da479



reply via email to

[Prev in Thread] Current Thread [Next in Thread]