DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:references:from:subject:message-id:date
	:mime-version:in-reply-to:content-type; q=dns; s=default; b=PF76
	gBihmzj16ivMA4TGz4UvPQCNlItl343RqLITFXpZ4Z4zOhCsK3RrSz27lKtdPq5w
	rvTvqqp94qHOpggPJI5RxaHRX6bEKarLB/EiRgFVhNHXgRwTTKL1q5hcTWmRSwjT
	ZyRyTpfGDqQohhGroCNbWG5M23UZ73MLu+bvSOU=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
References: <461ebfd6-3497-68db-61e4-ff7061ebfd50 AT gmail DOT com> <0d0e9175-b5a7-bcbf-efbc-82fa517ef5e2 AT SystematicSw DOT ab DOT ca>
From: LRN <lrn1986 AT gmail DOT com>
Subject: Re: Are my emails being filtered out?
Message-ID: <4be758f6-287a-11ea-7978-a329dd86e097@gmail.com>
Date: Wed, 17 Apr 2019 19:13:44 +0300
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <0d0e9175-b5a7-bcbf-efbc-82fa517ef5e2@SystematicSw.ab.ca>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="VGemRod48YGG0k1qtGulrKzhkAP8BQZhP"

--VGemRod48YGG0k1qtGulrKzhkAP8BQZhP
Content-Type: multipart/mixed; boundary="6mbmVkXFH8PVpouJaQcp8uJk1YQSGlJq6";
 protected-headers="v1"
From: LRN <lrn1986 AT gmail DOT com>
To: cygwin AT cygwin DOT com
Message-ID: <4be758f6-287a-11ea-7978-a329dd86e097 AT gmail DOT com>
Subject: Re: Are my emails being filtered out?


--6mbmVkXFH8PVpouJaQcp8uJk1YQSGlJq6
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 17.04.2019 18:30, Brian Inglis wrote:
> 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?
>=20
> The best way to initiate discussion may be replying to a previous post ab=
out a
> package in the relevant group with patches (see below), or an email with =
a new
> well written, specific subject.

TL/DR version: i'm doing things correctly, AFAIU, CMIIW.


I was sending messages to this list, the subject was 'cygwin port of glib'.
That seems specific enough for me. If there's a detail that i forgot to men=
tion
in the subject, please advice, i'll gladly include it. There was initially a
reply (by Erik M. Bray), so i guess it could also be counted as "replying t=
o a
previous post" as well.

> 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 part=
icipate
> or work upstream, in other distros, packages, products, or standards grou=
ps.
> 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, 1=
997.

I probably wasn't clear. "A few months" is not the time that i can devote to
this topic. It's the soft deadline that i've been given.

The specific person i'm trying to communicate with doesn't seem to be on
vacation (there was a message from that person in this mailing list yesterd=
ay,
and eight days ago as well). As for being busy, i'm ok with an "i'm busy, w=
ill
reply later" reply. I certainly not expect anyone to drop everything and de=
vote
all their time to researching the issues i raised. I do expect some kind of
acknowledgement though. Guess i'm one of those people that don't like being
ignored (and that's how it looks like, from where i'm sitting).

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

I'm not submitting any patch or a package, i have a question about a patch =
that
was already submitted in the past.
cygwin-announce is obviously the wrong choice for this.
cygwin-apps also seems a bad choice (i'm not a maintainer, and it's forbidd=
en
to subscribe to that list to ask questions about packages, which is what i =
want
to ask).
cygwin-developers is for devs only (i was already asked to not to post ther=
e in
the past, when i had a question tangentially-related to Cygwin, and my curr=
ent
question certainly does not qualify as "related to Cygwin development").
cygwin-patches is for patch submissions only
cygwin-talk is not for technical questions.
That leaves this list ("In general, you should send questions and bug repor=
ts
here").

The website that corresponds to the package in question is
http://cygwinports.org/ , though its mailing list prescriptions are somewhat
contradictory ("Issues with packages provided by Cygwin Ports in the Cygwin
distribution should use the usual Cygwin mailing lists[i.e. this list?].
Please, do NOT send messages about the packages previously shipped here to =
the
cygwin.com lists[i.e. this list?]."). Maybe i'm lacking some crucial piece =
of
context information (does "packages previously shipped here" have some spec=
ial
meaning?).

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

cygwinports github site (section? repository group? user? I don't know how =
it's
called on github) seems kind of bare. Looks like a mirror to me (i could be
wrong, of course). No issues or PRs for the glib2.0 package either, so i ca=
n't
be sure that anything i submit there is going to be noticed by anyone.


--6mbmVkXFH8PVpouJaQcp8uJk1YQSGlJq6--

--VGemRod48YGG0k1qtGulrKzhkAP8BQZhP
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE4MWzR43wYaAzEA49ja3pJ2dZunQFAly3ULgACgkQja3pJ2dZ
unTG1xAAi4/b9MQLOfNCTpEc9MzYztGI9b/vkz8iM/HBB3qNvLSonfNQwf3AGhpX
ZhDo9QCDFRVYoFpm26p7RpJ8urzVPNJRZCiSntCKpUGSeIZBvV4UV2ZF7Tp/CHje
5jmAeDhFSP1uw8ocBX7dR47xW0J7qrdJWbKB+bS+4tCJKSWmF5uiARBaKVinVK3k
YhnVRwySiFrex7UYCGTyro/rvCxbfQGzZJoyD7pLoWnmYs+QmVXEm2RjJn3EeaND
V6ZLBTcSX/HDLpgodUiZa/vBpUIT0IlZ0yS8QnUT06q2c7/hBqkFG7z/VudZK1NT
utDXgZ2jQLSs/91BnE2qlk5qPKuQ2nUEZj/d6sDQDUHCkwJWnXOAh1KHZ/lB+7ki
IhwRtJY7MGIhlMAj0Fr5M82GzL/po02P4ZPSOD3fm1udTsZqifIPfVYNzIz1d0WK
KDVFedDX/GKg/pkvIY4xeX0zSZ53tNRFK3dzuPSSLGi/QcK1OZMY8ZTj+hdYS2eX
NQSFCDMjR9RTH6EuvwgXDUonsih5I3ZDQS3DmnwiX7Ni+lzXtL8118UG2nMTPzit
oBbgRTTSg88gTATtLu17x03Xk6XzLO7ZetCwNrMGPhph9BCIbntf1LjJCkxCjBy/
kPGkiuu0vjHrSbQpnF6uv8Bc+iYFHfov8xYAKKruB2Kod5cAkPw=
=kb45
-----END PGP SIGNATURE-----

--VGemRod48YGG0k1qtGulrKzhkAP8BQZhP--