From: Stefan Kangas <stefan@marxist.se>
To: Alan Mackenzie <acm@muc.de>, emacs-devel@gnu.org
Subject: Re: Please stop making extra unnecessary work for us all.
Date: Tue, 12 Oct 2021 08:00:57 -0700 [thread overview]
Message-ID: <CADwFkmn3QF7c7KxsjYrxsF3A3pAUqr=9wFuvSgwaEvS2RtrNqQ@mail.gmail.com> (raw)
In-Reply-To: <YWWB5/qaVcJTPFoP@ACM>
Alan Mackenzie <acm@muc.de> writes:
> Many non-functional changes have been made in CC Mode. That
> additionally means that patches from standalone CC Mode are even less
> likely to apply cleanly in the Emacs branches than they were already.
> That means extra unwanted tedious work for me.
>
> And what are these changes? In at least two instances the case of a
> letter in warning messages following a colon was changed from lower to
> upper. Or was it the other way around? Come on, please, this is
> madness. Who would even notice the case of a letter after a colon in a
> warning message, much less care about it?
I do apologize if these changes lead to a large amount of extra work for
you. I'm not familiar with how CC-mode is developed, so I had assumed
that you would merge the Emacs tree into yours or the other way around,
which seems to be the most common solution to merge conflicts. I will
think twice before making any changes to cc-mode in the future.
The background is this:
I was running checkdoc in an automated way on the entire Emacs codebase.
This allowed me to fix many real issues in our documentation and clear
violations of our style. Every time there was an issue, if I could fix
it, I did, as it slowed this process down -- for me, and anyone that
might do this later. (Checkdoc stops on every single one for review.)
Some of them I couldn't fix, so I left them alone.
If someone wants to, they can now run checkdoc on all our Lisp code in
an automated way and relatively quickly find any newly introduced
issues, for example shortly before releasing a new version. My hope is
that this will lead to more consistency in our documentation and
messages. I expect that you value such things as much as I do.
Parts of your message unfortunately seems to be suggesting that these
changes were insignificant and/or useless taken as a whole. I think
that such a view is mistaken, and misses the point. For example, one
outcome of this work was improvements to checkdoc.el, another was an
improvement to our coding conventions. These things would not have
happened without first running checkdoc.el on our code.
Your claim that some of the changes were minor is true. I cannot agree
that they were therefore not worth doing; if you take such a line of
reasoning too far, we should also not run spell checkers, as typos don't
matter. Most of the changes under discussion are clear mistakes that
should have been fixed.
But I concede that some changes might have slipped through that were not
very important to make. I'm only human, I do my best. I hope that you
can accept my limitations and mistakes in this regard. Meanwhile, I'm
willing to accept that the best analogy you could find here is
"whitespace changes".
next prev parent reply other threads:[~2021-10-12 15:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 12:39 Please stop making extra unnecessary work for us all Alan Mackenzie
2021-10-12 12:44 ` Lars Ingebrigtsen
2021-10-12 12:55 ` Campbell Barton
2021-10-12 16:16 ` Finding the culprit (was: Please stop making extra unnecessary work for us all) Stefan Monnier
2021-10-12 16:40 ` Please stop making extra unnecessary work for us all Stefan Kangas
2021-10-12 13:36 ` dick
2021-10-12 15:00 ` Stefan Kangas [this message]
2021-10-12 23:20 ` Jean-Christophe Helary
2021-10-12 16:09 ` CC-mode fork (was: Please stop making extra unnecessary work for us all) Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkmn3QF7c7KxsjYrxsF3A3pAUqr=9wFuvSgwaEvS2RtrNqQ@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).