From: Eli Zaretskii <eliz@gnu.org>
To: Amin Bandali <bandali@gnu.org>
Cc: 50009@debbugs.gnu.org, dick.r.chiang@gmail.com, jp@neverwas.me
Subject: bug#50009: 28.0.50; add CRLF to outgoing ERC protocol logger lines
Date: Thu, 16 Sep 2021 08:42:35 +0300 [thread overview]
Message-ID: <83ilz19ius.fsf@gnu.org> (raw)
In-Reply-To: <87bl4ts7xv.fsf@gnu.org> (message from Amin Bandali on Wed, 15 Sep 2021 20:03:24 -0400)
> From: Amin Bandali <bandali@gnu.org>
> Date: Wed, 15 Sep 2021 20:03:24 -0400
> Cc: 50009@debbugs.gnu.org, "J.P." <jp@neverwas.me>
>
> dick writes:
>
> > Sigh, it pains me to have to add to the verbiage maelstrom that is debbugs
> > when the antiquity of GNU patch is self-evident.
>
> To be clear, GNU is by far not the only project that uses patch-driven
> workflows.
This discussion doesn't belong here. Here we discus a specific issue
submitted to the Emacs issue tracker. Broad discussions about our
development workflows should be held on emacs-devel. Please move it
there (if you must have this discussion, which is about the umpteenth
time it is being brought up, including very recently).
Whatever you do, please STOP discussing it here. Right now, the only
effect this has is to make following the discussions of bug#50009 much
harder by polluting it with unrelated messages, which are not even
tangents.
next prev parent reply other threads:[~2021-09-16 5:42 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
2021-09-16 5:42 ` Eli Zaretskii [this message]
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=83ilz19ius.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=50009@debbugs.gnu.org \
--cc=bandali@gnu.org \
--cc=dick.r.chiang@gmail.com \
--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).