all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: 50009@debbugs.gnu.org, bandali@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: Fri, 17 Sep 2021 09:24:44 +0300	[thread overview]
Message-ID: <83r1dn90sz.fsf@gnu.org> (raw)
In-Reply-To: <E1mR1Vs-00022n-5k@fencepost.gnu.org> (message from Richard Stallman on Thu, 16 Sep 2021 20:13:56 -0400)

> From: Richard Stallman <rms@gnu.org>
> Date: Thu, 16 Sep 2021 20:13:56 -0400
> Cc: 50009@debbugs.gnu.org, bandali@gnu.org, jp@neverwas.me
> 
> Can a PR-based workflow be made to operate via email, in a way that
> doesn't require a net connection?  (Except, at some later time, for
> committing a change.)  That is a requisite for us.

As I said, we should NOT discuss these matters in an unrelated bug
report.

Our prerequisite is not to have the PR workflow work via email, it is
that the maintainer's part of the workflow could be done via email.





  parent reply	other threads:[~2021-09-17  6:24 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
2021-09-17  0:13         ` Richard Stallman
2021-09-17  1:17           ` dick
2021-09-17  6:24           ` Eli Zaretskii [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83r1dn90sz.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 \
    --cc=rms@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.