From: Jon Turney <jon.turney@dronecode.org.uk>
To: rajesh kesavan <rajeshrube@gmail.com>,
The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Getting return code "127" after execution of program
Date: Sun, 4 Jun 2023 13:01:02 +0100 [thread overview]
Message-ID: <b32b2a16-a7fa-119a-4d6d-79a0d1b8e675@dronecode.org.uk> (raw)
In-Reply-To: <c566b9b5-c5bf-a892-3572-be63531effa1@cs.umass.edu>
On 02/06/2023 13:42, Eliot Moss via Cygwin wrote:
> On 6/2/2023 5:58 AM, rajesh kesavan via Cygwin wrote:
>> Hi,
[...]
> (I also don't think you needed to include all those lists in your
> original post; cygwin@cygwin.com would be enough for now, so I have
> trimmed other lists from my response.)
Indeed not.
Rajesh,
You should only ever send mail to the mailing list 'owner' address if
you have a problem with your subscription to the mailing list.
Therefore, it is probably never appropriate to send mail to both the
list, and the owner of the list.
Further, cygwin-developers@cygwin.com is explicitly described as for
"contributing to the development of Cygwin [...] If you have an issue
and hope that someone will look into it for you then please do not send
email here". That seems a clear request to not send this kind of mail
there.
By spamming all these addresses, you signal that you are impatient,
inconsiderate and not respectful of the boundaries of others.
This won't help you engage members of our community who are willing to
help you solve your problem.
Please don't do it ever again.
next prev parent reply other threads:[~2023-06-04 12:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 9:58 rajesh kesavan
2023-06-02 12:42 ` Eliot Moss
2023-06-04 12:01 ` Jon Turney [this message]
2023-06-02 15:07 ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2023-06-02 23:28 ` Brian Inglis
2023-06-03 17:35 ` Andrey Repin
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=b32b2a16-a7fa-119a-4d6d-79a0d1b8e675@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=rajeshrube@gmail.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).