From: dick <dick.r.chiang@gmail.com>
To: Amin Bandali <bandali@gnu.org>
Cc: 50009@debbugs.gnu.org, "J.P." <jp@neverwas.me>
Subject: bug#50009: 28.0.50; add CRLF to outgoing ERC protocol logger lines
Date: Wed, 15 Sep 2021 12:35:00 -0400 [thread overview]
Message-ID: <87lf3xpzkb.fsf@dick> (raw)
In-Reply-To: <87lf3y7pic.fsf@gnu.org> (Amin Bandali's message of "Tue, 14 Sep 2021 18:37:15 -0400")
Sigh, it pains me to have to add to the verbiage maelstrom that is debbugs
when the antiquity of GNU patch is self-evident.
A maintainer's sanity is inversely related to how much reading he has to do.
In a PR-based workflow, the changeset is unambiguous. On a platform like
Github, the changeset is manifest (in pretty colors) from the "Files Changed"
tab in a PR submission. Eleventh-hour revisions get incorporated without fuss
via the mild genius of git.
Here, OP has submitted several changesets, of which only the chronologically
latest he wishes the maintainer to consider. To ascertain this fact, the
maintainer must read, and recall his happiness is inversely proportional to
how much reading he has to do.
In a cluster**** like bug#45474 where literally every one and their third
cousin is espousing a changeset, the maintainer not only has to read, he has
to decide, and that is a whole other circle of hell. The programmer's
tendency to pontificate and obfuscate (of which the present missive is a fine
example) does not help matters.
next prev parent reply other threads:[~2021-09-15 16:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 14:26 bug#50009: 28.0.50; add CRLF to outgoing ERC protocol logger lines J.P.
2021-09-12 12:04 ` J.P.
2021-09-13 0:52 ` J.P.
2021-09-13 3:04 ` J.P.
2021-09-14 9:22 ` J.P.
2021-09-14 10:44 ` dick
2021-09-14 22:37 ` Amin Bandali
2021-09-15 16:35 ` dick [this message]
2021-09-15 17:15 ` Eli Zaretskii
2021-09-15 17:49 ` dick
2021-09-15 18:13 ` Eli Zaretskii
2021-09-16 0:03 ` Amin Bandali
2021-09-16 0:20 ` dick
2021-09-16 5:42 ` Eli Zaretskii
2021-09-17 0:13 ` Richard Stallman
2021-09-17 1:17 ` dick
2021-09-17 6:24 ` Eli Zaretskii
2021-09-16 13:36 ` Lars Ingebrigtsen
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=87lf3xpzkb.fsf@dick \
--to=dick.r.chiang@gmail.com \
--cc=50009@debbugs.gnu.org \
--cc=bandali@gnu.org \
--cc=jp@neverwas.me \
/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).