From: Fergus Daly <fergusd84@outlook.com>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Cc: Fergus Daly <fergusd84@outlook.com>
Subject: Long lines in posts to this mailing list
Date: Wed, 14 Dec 2022 10:53:47 +0000 [thread overview]
Message-ID: <DB6P18901MB00558ECDB2DB0E41E52557F3A4E09@DB6P18901MB0055.EURP189.PROD.OUTLOOK.COM> (raw)
What causes long lines without word wrap in posts to this list (such as the immediately preceding
"gcc v.11.3.0 failing") and how can they be avoided?
(They are very inconvenient - sorry!)
next reply other threads:[~2022-12-14 10:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 10:53 Fergus Daly [this message]
2022-12-14 11:10 ` Adam Dinwoodie
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=DB6P18901MB00558ECDB2DB0E41E52557F3A4E09@DB6P18901MB0055.EURP189.PROD.OUTLOOK.COM \
--to=fergusd84@outlook.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).