From: dick <dick.r.chiang@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Please stop making extra unnecessary work for us all.
Date: Tue, 12 Oct 2021 09:36:23 -0400 [thread overview]
Message-ID: <8735p65prc.fsf@dick> (raw)
In-Reply-To: <YWWB5/qaVcJTPFoP@ACM> (Alan Mackenzie's message of "Tue, 12 Oct 2021 12:39:03 +0000")
I've observed similar bristling over superfluous changes in the past. I can
only assume the bristlers are of "a certain age" (which I am as well) who cut
their teeth on CVS or RCS.
It is a bad state of affairs when your development process cannot tolerate
whitespace changes since at the core of every good developer is an
insufferable grammarian who obsesses over straight lines and chamfered edges.
Git is singularly designed to make these cosmetic changes non-events via
switches like `git diff -b` and `git merge -X ours`.
I've long grown accustomed to digging several levels to properly assign
git-blame. Generally if the code in question is complicated enough, the
person responsible is never the first name that shows up.
next prev parent reply other threads:[~2021-10-12 13:36 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 [this message]
2021-10-12 15:00 ` Stefan Kangas
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=8735p65prc.fsf@dick \
--to=dick.r.chiang@gmail.com \
--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).