public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Cc: "Pms, Balamurugan (GE Digital, consultant)" <balamurugan.pms@ge.com>
Subject: Re: Cygwin issue
Date: Thu, 4 Jun 2020 08:19:42 -0600	[thread overview]
Message-ID: <8f03af5b-f812-3069-905e-596b4e462961@SystematicSw.ab.ca> (raw)
In-Reply-To: <1d5e4985-7dc6-214c-de7b-f984a7bfdc39@towo.net>

On 2020-05-28 06:04, Thomas Wolff wrote:
>> Cygwin issue
> 
> Please use descriptive mail subjects. It's really too bothersome to follow
> issues otherwise.

Cygwin supports 11000+ packages - please be specific in the subject and detailed
in the body - we do not know what you are doing with it - support is by busy
volunteers so if your subject does not contain a keyword they are responsible
for, it may be treated as junk and they may not even see your email.

Neither problem reporters nor maintainers may be native English speakers, and
even if they are, verbal descriptions of (selected, possibly insignificant)
problem symptoms are typically unhelpful, unless you have already diagnosed the
problem and are proposing a fix.

Please always show command lines and output with error messages or similarly
specific input and output, as attached logs or text copy and paste (into a log
file to be attached if long), not screenshots which will get your mail rejected
on these lists, and which are typically so low resolution, small, or the
graphics are so small they are indecipherable anyway.

Please read and follow:

	https://cygwin.com/problems.html

which references:

	http://www.catb.org/~esr/faqs/smart-questions.html

-- 
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.
[Data in IEC units and prefixes, physical quantities in SI.]

      reply	other threads:[~2020-06-04 14:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-28 11:52 Pms, Balamurugan (GE Digital, consultant)
2020-05-28 12:04 ` Thomas Wolff
2020-06-04 14:19   ` Brian Inglis [this message]

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=8f03af5b-f812-3069-905e-596b4e462961@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=balamurugan.pms@ge.com \
    --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).