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: Are my emails being filtered out?
Date: Wed, 17 Apr 2019 15:30:00 -0000	[thread overview]
Message-ID: <0d0e9175-b5a7-bcbf-efbc-82fa517ef5e2@SystematicSw.ab.ca> (raw)
In-Reply-To: <461ebfd6-3497-68db-61e4-ff7061ebfd50@gmail.com>

On 2019-04-17 02:06, LRN wrote:
> 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? 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 best way to initiate discussion may be replying to a previous post about a
package in the relevant group with patches (see below), or an email with a new
well written, specific subject.
All participants are volunteers, with busy jobs, lives, or families, who also
take trips and vacations.
Some maintain dozens, hundreds, or thousands of Cygwin packages, may participate
or work upstream, in other distros, packages, products, or standards groups.
You may have months but they may have only minutes or seconds for a topic -
respect that: "We are now living on Internet time" - Andy Grove, Intel, 1997.

The relevant groups for patch submission and discussion are cygwin-apps for
apps, cygwin-patches for winsup..., newlib for other library files, to which you
must subscribe, or the upstream maintainer via email on the source site,
normally using git format-patch/send-email against the latest sources, with well
written, specific subjects and commit log entries.

If the upstream source site has public email archives, issue or bug tracker, you
may be able to search for relevant Cygwin or maintainer content, or you may have
to ask the maintainer if an issue has already been raised with them.

-- 
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.

--
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

  reply	other threads:[~2019-04-17 15:30 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 [this message]
2019-04-17 15:57   ` Chris Wagner
2019-04-17 16:13   ` LRN
2019-04-17 17:05 ` Achim Gratz
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=0d0e9175-b5a7-bcbf-efbc-82fa517ef5e2@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).