public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Are my emails being filtered out?
Date: Wed, 17 Apr 2019 17:05:00 -0000	[thread overview]
Message-ID: <87sgug36mm.fsf@Rainer.invalid> (raw)
In-Reply-To: <461ebfd6-3497-68db-61e4-ff7061ebfd50@gmail.com> (LRN's message	of "Wed, 17 Apr 2019 11:06:15 +0300")

LRN writes:
> Subj. I've been sending emails to this list for a couple of weeks now, and no
> one replies. Do these messages come through at all?

Yes, they do just fine.

> I know for a fact that the messages do end up in the ML archives, so
> they reach at least *some* places.  In case this message is being read
> by anyone: i'm looking either for Yaakov Selkowitz, or for anyone who
> maintains the glib Cygwin package. Please help, i only have a few
> months.

The inofficial protocol for reaching out to a package maintainer is to
put "[Attn. Maintainer] <pkg>" in the subject of your mail.  Said
maintainer may be currently unavailable or busy with other stuff, so
please give her/him ample time to respond, i.e. at least two or three
weeks before following up.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2019-04-17 17:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-17  8:06 LRN
2019-04-17 15:30 ` Brian Inglis
2019-04-17 15:57   ` Chris Wagner
2019-04-17 16:13   ` LRN
2019-04-17 17:05 ` Achim Gratz [this message]
2019-04-17 17:40   ` LRN

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=87sgug36mm.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).