From: David Sastre <d.sastre.medina@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: lost announcements
Date: Mon, 24 Oct 2011 21:31:00 -0000 [thread overview]
Message-ID: <20111024213123.GB5193@jethro.local.lan> (raw)
In-Reply-To: <uilba7l64gjjhsprmcea02t9fadpk61o85@4ax.com>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
On Mon, Oct 24, 2011 at 05:20:52PM -0400, Andrew Schulman wrote:
> > On Mon, Oct 24, 2011 at 04:16:18PM -0400, Andrew Schulman wrote:
> > > This morning I sent 4 package update announcements to cygwin-announce. Two of
> > > them (socat, lftp) were posted, but the other two (stunnel, sng) haven't shown
> > > up yet. Meanwhile, other later announcements have been posted.
> > >
> > > Are the missing messages held up in the queue? Anything I need to do about
> > > that? Or, should I resend them?
> >
> > I have received them, and they both show in the web:
> >
> > http://cygwin.com/ml/cygwin-announce/2011-10/msg00036.html
> > http://cygwin.com/ml/cygwin-announce/2011-10/msg00035.html
>
> Hm, you're right. But the odd thing is that they weren't posted to the cygwin
> list, which is where I read them: http://cygwin.com/ml/cygwin/2011-10/.
>
> Any idea why?
Nope. And I'm afraid I can't help there.
--
Huella de clave primaria: AD8F BDC0 5A2C FD5F A179 60E7 F79B AB04 5299 EC56
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 230 bytes --]
next prev parent reply other threads:[~2011-10-24 21:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 20:16 Andrew Schulman
2011-10-24 20:34 ` David Sastre
2011-10-24 21:21 ` Andrew Schulman
2011-10-24 21:31 ` David Sastre [this message]
2011-10-24 23:48 ` Christopher Faylor
2011-10-25 13:17 ` Andrew Schulman
2011-10-25 15:19 ` Christopher Faylor
2011-10-26 6:27 ` Andrew Schulman
2011-10-26 7:25 ` Corinna Vinschen
2011-10-26 13:55 ` 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=20111024213123.GB5193@jethro.local.lan \
--to=d.sastre.medina@gmail.com \
--cc=cygwin-apps@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).