From: David Finnie <david.finnie68@gmail.com>
To: cygwin@cygwin.com
Subject: Update to "Reporting Guidelines" on the cygwin site
Date: Tue, 21 Jan 2020 06:52:00 -0000 [thread overview]
Message-ID: <e3b0a6e5-aee5-4f08-888e-aa7e1a4175f2@gmail.com> (raw)
In-Reply-To: <5b4e8b66-49d5-8150-c884-96a2ce3ff84b@gmail.com>
> Please bottom posting and trim here.
(Above is copied from a recent post about a problem report.)
Being a fairly new member of this mailing list, I did carefully read the
guidelines about using the mailing list, but there was no mention of no
top posting etc. And yes, I did top post myself one time because it is
my usual habit because it is standard in the business world (for better
or worse) and some people even take offence if you address each point
because they feel that you are picking apart their entire conversation
and being confrontational. I know it is not meant that way here, but it
becomes a habit to not do it, and to top post instead.
I've noticed that several active list members have had to mention this
no-top-posting policy (and yes, I was on the receiving end also).
Can I suggest that whoever maintains the web page with the main
discussion about mailing lists updates the instructions ? Then we can
hopefully avoid some of the angst and constant need to remind people ?
Dave
--
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
next prev parent reply other threads:[~2020-01-21 6:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 0:08 Getting Python on Windows points USER_HOME R Steiger
2020-01-21 3:33 ` Marco Atzeri
2020-01-21 5:47 ` R Steiger
2020-01-21 6:31 ` Marco Atzeri
2020-01-21 6:52 ` David Finnie [this message]
2020-01-21 9:03 ` Update to "Reporting Guidelines" on the cygwin site Doug Henderson
2020-01-21 9:34 ` Getting Python on Windows points USER_HOME Doug Henderson
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=e3b0a6e5-aee5-4f08-888e-aa7e1a4175f2@gmail.com \
--to=david.finnie68@gmail.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).