From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: overseers@sourceware.org, cygwin-announce-owner@sourceware.org
Cc: Sourceware Email Support <postmaster@sourceware.org>,
cygwin-apps@cygwin.com
Subject: cygwin-announce notices not forwarding to cygwin list
Date: Sun, 15 Mar 2020 11:34:26 -0600 [thread overview]
Message-ID: <ef4ae3e3-1fb8-4d4a-baa1-71120a28231a@SystematicSw.ab.ca> (raw)
In-Reply-To: <72d7f27b-8ccb-2c05-ebea-8615a0050647@gmail.com>
> On Sat, 14 Mar 2020 15:54:31 +0100, Marco Atzeri wrote:
>> Am 09.03.2020 um 22:22 schrieb Jon Turney:
>>> On 06/03/2020 18:27, Jon Turney wrote:
>>>> On 04/03/2020 13:33, Jon Turney wrote:
>>>>>
>>>>> Assuming this migration goes ahead as planned this weekend:
>>>>>
>>>>> * I'll stop package upload processing sometime on Friday
>>>>>
>>>>> * An announcement will be made when package upload processing is
>>>>> restored.
>>>
>>> package maintainer sftp and git is working.
>>>
>>> calm is running again.
>
> it seems that the forwarding from cygwin-announce to cygwin
> mailing list is not active anymore
Hi folks,
Could you please look at why cygwin-announce notices are no longer forwarding to
cygwin list post-migration, when you have some time from higher priority work,
or inform the folks responsible if not already CCed.
--
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-03-15 17:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <72d7f27b-8ccb-2c05-ebea-8615a0050647@gmail.com>]
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=ef4ae3e3-1fb8-4d4a-baa1-71120a28231a@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-announce-owner@sourceware.org \
--cc=cygwin-apps@cygwin.com \
--cc=overseers@sourceware.org \
--cc=postmaster@sourceware.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.
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).