From: dick <dick.r.chiang@gmail.com>
To: Amin Bandali <bandali@gnu.org>
Cc: 50009@debbugs.gnu.org
Subject: bug#50009: 28.0.50; add CRLF to outgoing ERC protocol logger lines
Date: Wed, 15 Sep 2021 20:20:22 -0400 [thread overview]
Message-ID: <87wnnhnzg9.fsf@dick> (raw)
In-Reply-To: <87bl4ts7xv.fsf@gnu.org> (Amin Bandali's message of "Wed, 15 Sep 2021 20:03:24 -0400")
> I've seen my fair share of similarly long yet considerably worse GitHub
> discussions
"Considerably worse" would be an understatement. Verbosity is a function of
the age and number of participants, and Github skews unfavorably in both those
categories.
My point was the verbosity, a systemic cost to doing business, does not
under a PR-based workflow occlude the proposed changeset, whereas under
"wonderful" Debbugs the proliferation of proposed patches could.
Your raising the example of native-comp merely reinforces my point that
branch-based schemes are superior to ad hoc email-based ones.
It's clear we've already made our minds about it. But you asked, so I
answered. Pardon the "interference" to those trying to "do their job."
next prev parent reply other threads:[~2021-09-16 0:20 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
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 [this message]
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=87wnnhnzg9.fsf@dick \
--to=dick.r.chiang@gmail.com \
--cc=50009@debbugs.gnu.org \
--cc=bandali@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).