From: Bart Schaefer <schaefer@brasslantern.com>
To: Rudi C <rudiwillalwaysloveyou@gmail.com>
Cc: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: [Bug] Unexpected bug suspension
Date: Thu, 21 May 2020 11:10:33 -0700 [thread overview]
Message-ID: <CAH+w=7aUA4LxOsAcRjujXOH1Pb=CsxoBk3Xtnf3yBbUvtROooQ@mail.gmail.com> (raw)
In-Reply-To: <CAE9z9A1ZOYyBcKwXjXD4JBKiUSpK1gSqRBz_GEqLvEJmtwdjvw@mail.gmail.com>
On Thu, May 21, 2020 at 5:39 AM Rudi C <rudiwillalwaysloveyou@gmail.com> wrote:
>
> Googling for "how to use mailing list effectively" returns marketing bullshit. ...
Well, one way is to occasionally put line breaks in your wall of text.
Another is to put your reply below an edited-down excerpt of the
conversation instead of at the top of everything that's been written
before. I know that takes an annoying extra few seconds.
next prev parent reply other threads:[~2020-05-21 18:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 9:23 Mikael Magnusson
2020-05-21 12:39 ` Rudi C
2020-05-21 18:10 ` Bart Schaefer [this message]
2020-05-21 19:01 ` Bart Schaefer
2020-05-21 20:15 ` Rudi C
2020-05-21 21:00 ` Bart Schaefer
2020-05-21 16:30 ` Daniel Shahaf
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='CAH+w=7aUA4LxOsAcRjujXOH1Pb=CsxoBk3Xtnf3yBbUvtROooQ@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=rudiwillalwaysloveyou@gmail.com \
--cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).