public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Bill Stewart <bstewart@iname.com>
To: cygwin@cygwin.com
Subject: Re: Two naive questions
Date: Mon, 20 Apr 2020 14:44:41 -0600	[thread overview]
Message-ID: <CANV9t=SbhaFaLZTLq50pQEbrKYBvvzWFSgkv_K+STvAaC23bSQ@mail.gmail.com> (raw)
In-Reply-To: <20200420200921.GA10790@cgf.cx>

On Mon, Apr 20, 2020 at 2:09 PM Christopher Faylor wrote:

> With mailman, if you click on a message in the archives and then click
> on the email address at the top, your mail client of choice will be
> opened with correct "In-Reply-To" set.  If you want to reply to the list
> then replace the "To" with the email address of the mailing list.  You
> can also download the mailbox-formatted archive, read it with a client
> like "mutt" and reply that way.

So it is _possible_, but not exactly user-friendly (you're presuming
that end-users even understand these instructions). What if a user is
limited to a web-based mail client, for example, and has no way to
access said options? (I think it goes without saying that a "use a
better mail client" response is not feasible, at least for some users,
in addition to possibly sounding a bit elitist.)

Aside from this, in my opinion, the above instructions are an awkward
(IMO) workaround due to limitations inherent in trying to use email
for something it wasn't really designed for (again: just my opinion).

> OTOH, most message boards have a way to freeze old discussions and
> discourage resurrecting dead threads.

That depends on who administers the forum. That's not necessarily an
inviolable rule.

Again - not trying to start a controversy here - just pointing out
that a mailing list has some limitations. (After all, web-based
discussion forums were invented for a reason.)

Bill

  reply	other threads:[~2020-04-20 20:45 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16 20:21 Fergus Daly
2020-04-17  5:10 ` Marco Atzeri
2020-04-17 11:17   ` Fergus Daly
2020-04-17 17:31     ` Brian Inglis
2020-04-17 17:49   ` Stephen Carrier
2020-04-17 18:16     ` Andrey Repin
2020-04-17 18:44       ` Brian Inglis
2020-04-20 17:20         ` Stephen Carrier
2020-04-20 17:41           ` Bill Stewart
2020-04-20 18:11             ` Eliot Moss
2020-04-20 18:51               ` Bill Stewart
2020-04-20 20:09             ` Christopher Faylor
2020-04-20 20:44               ` Bill Stewart [this message]
2020-04-20 23:51                 ` Christopher Faylor
2020-04-21 16:47               ` Stephen Carrier
2020-04-22  9:57             ` Andrey Repin
2020-04-23 16:49               ` Stephen Carrier
2020-04-23 19:13                 ` Christopher Faylor
2020-04-23 19:33                   ` Christopher Faylor
2020-04-24 18:58                   ` Stephen Carrier
2020-04-25 15:18                     ` Christopher Faylor
2020-04-20 17:59           ` Brian Inglis
2020-04-20 20:14             ` Christopher Faylor
2020-04-21 18:33               ` Brian Inglis
2020-04-21 20:30                 ` Mailing list musings (was Re: Two naive questions) Christopher Faylor
2020-04-19  2:58 ` Two naive questions Christopher Faylor

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='CANV9t=SbhaFaLZTLq50pQEbrKYBvvzWFSgkv_K+STvAaC23bSQ@mail.gmail.com' \
    --to=bstewart@iname.com \
    --cc=cygwin@cygwin.com \
    /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.
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).