public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Two naive questions
Date: Mon, 20 Apr 2020 11:59:08 -0600	[thread overview]
Message-ID: <9d2da84a-61db-ea3e-a70b-9e8b2e42fe4f@SystematicSw.ab.ca> (raw)
In-Reply-To: <20200420172017.GA17660@iguana.crashland.org>

On 2020-04-20 11:20, Stephen Carrier wrote:
> On Fri, Apr 17, 2020 at 12:44:30PM -0600, Brian Inglis wrote:
>> On 2020-04-17 12:16, Andrey Repin wrote:
>>> Greetings, Stephen Carrier!
>>>> I remember having had the same confusion the first few times I initiated
>>>> threads.
>>
>>> When you start a new thread, do not reply to existing threads.
>>> It's that simple.
>>
>> Indeed - proper mail and news readers use References not Subject headers for
>> threading when available, so your new topic will be lost under an old thread.
> 
> I think the OP's first question was asking how to effectively join
> an existing thread when one is browsing the recent archives and not
> subscribed to the list.

As the next response and his reply make clear, he was asking about preperly
replying after subscribing.

> Joining the list after seeing a question one would like to answer
> doesn't help, because the message you would like to respond to has
> already gone by.
> 
> I think a good solution would be to get the message number from the web
> archive and request that a particular message be sent to you.  Then you
> could respond to that message and join the thread properly.
> 
> However, there doesn't seem to be a way to do that.  I used to be notified
> how to retrieve messages I had missed (due to bouncing) but the method
> did not work.  Furthermore, the mailman faq doesn't mention any way to
> do this.

The new server ml archive does not seem to offer the metadata available on the
previous server and archive, and that is true of most archives that do not allow
replies: probably a good way to reduce space required by 50-90%, from what I can
see.
A subscribed user could provide you with the reply References header values.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

  parent reply	other threads:[~2020-04-20 17:59 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
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 [this message]
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=9d2da84a-61db-ea3e-a70b-9e8b2e42fe4f@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).