[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: master 95e8c7d 1/2: ; Fix typos
From: |
Stefan Kangas |
Subject: |
Re: master 95e8c7d 1/2: ; Fix typos |
Date: |
Sat, 10 Oct 2020 01:14:40 -0700 |
Eli Zaretskii <eliz@gnu.org> writes:
>> But it is true that it would be preferable if the code matched the
>> documentation. In the interest of consistency we are better off
>> sticking to one spelling. Note that we already had around 40 other
>> instances of "parsable" in our source tree.
>
> Since renaming symbols involves some pain, do we really need to be
> 100% consistent here?
I personally don't have a very strong opinion either way, FWIW.
- Re: master 95e8c7d 1/2: ; Fix typos, Robert Pluim, 2020/10/09
- Re: master 95e8c7d 1/2: ; Fix typos, Eli Zaretskii, 2020/10/09
- Re: master 95e8c7d 1/2: ; Fix typos, Stefan Kangas, 2020/10/09
- RE: master 95e8c7d 1/2: ; Fix typos, Drew Adams, 2020/10/09
- Re: master 95e8c7d 1/2: ; Fix typos, Eli Zaretskii, 2020/10/10
- Re: master 95e8c7d 1/2: ; Fix typos,
Stefan Kangas <=
- Re: master 95e8c7d 1/2: ; Fix typos, Robert Pluim, 2020/10/12
- Re: master 95e8c7d 1/2: ; Fix typos, Eli Zaretskii, 2020/10/12
- Re: master 95e8c7d 1/2: ; Fix typos, Stefan Kangas, 2020/10/16