From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Two naive questions
Date: Fri, 17 Apr 2020 11:31:32 -0600 [thread overview]
Message-ID: <a6769081-1ed5-a020-2369-395f3a61da66@SystematicSw.ab.ca> (raw)
In-Reply-To: <AM6PR03MB5282A63F0344EA760C7F4468A4D90@AM6PR03MB5282.eurprd03.prod.outlook.com>
On 2020-04-17 05:17, Fergus Daly via Cygwin wrote:
>>> usually it is just reply to the list on your mail program.
> Yeah, I now see how it all works. Thank you.
When Reply List doesn't work, pick Reply All and trim the To and Reply To
addresses to just the list address, and maybe a CC to what may be a
non-subscriber if you don't recognize them.
>>> Cygwin is a guest on it, we are not the maintainers.
> Understood. Thank you.
> On 17 April 2020 06:11, Marco Atzeri wrote:
> Am 16.04.2020 um 22:21 schrieb Fergus Daly via Cygwin:
>> I've been reading/writing to this list since 2001 or maybe earlier and
>> have only just Subscribe'd. Mainly because I have been aware when
>> contributing to a thread I have always broken it by not using Follow-up
>> properly, just artificially including the title prefix Re: in what is
>> essentially a new post.
>> Having Subscribe'd, I'm no clearer how to do this properly.
>> 1. Please can somebody point me to an instruction?
> usually it is just reply to the list on your mail program.
>> 2. Since when the new look provided by
>> https://cygwin.com/pipermail/cygwin/ ?
> new server for sourceware.org with new software in March
> https://sourceware.org/sourceware-wiki/MigrationStatus/
> Cygwin is a guest on it, we are not the maintainers.
>> Is there a way to default to the "legacy" look provided at, say,
>> https://sourceware.org/legacy-ml/cygwin/2019-04/
>> but not obviously available today (even by changing 2019 to 2020 in the
>> line above)?
>> (I've looked for what I had assumed would be a long conversation on this
>> change, but cannot find anything.)
Infrastructure issues are dealt with on:
https://sourceware.org/mailman/listinfo/overseers
and the move/migration was dealt with under:
https://sourceware.org/pipermail/overseers/2020q1/thread.html
(#start and #end anchors go to oldest and newest posts)
starting:
https://sourceware.org/pipermail/overseers/2020q1/016620.html
You can find mentions of overseers in some sourceware pages.
--
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.
next prev parent reply other threads:[~2020-04-17 17:31 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 [this message]
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
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=a6769081-1ed5-a020-2369-395f3a61da66@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).