From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Cygcheck.out sent to list causes email to get blocked (was Re: unset TMP Variable issue)
Date: Fri, 30 Aug 2019 01:42:00 -0000 [thread overview]
Message-ID: <f9a4583e-5026-735f-c1de-7ecba802cd80@SystematicSw.ab.ca> (raw)
In-Reply-To: <5D67B183.2080103@tlinx.org>
On 2019-08-29 05:05, L A Walsh wrote:
> On 2019/07/20 16:30, Nikos Balkanas wrote:
>>>
>>> Attached is the zipped cygcheck output with user names crossed out
>>>
>
> Worry, but your attachment of the output never came through. Neither
> did mind.
>
> Looks like the mailing list software discards cygcheck.out output now,
> which
> seems to make the error reporting process a bit broken?
Emails may only have plain text attachments: add cygwin.com/org/net and
sourceware.org to Thunderbird plain text domains max line length 80, 72, 64:
Tools/Options/Composition/General/Send Options/Text Format/[X]Send as plain text
Tools/Options/Composition/General/Send Options/[Convert to plain text]
Tools/Options/Composition/General/Send Options/Plain Text Domains/Add/cygwin.com
Tools/Options/Advanced/General/Config Editor/Search/wrap
or the equivalent in other MUAs.
--
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.
--
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
prev parent reply other threads:[~2019-08-29 21:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAxXO2E0edZafrjRHg7uk1CvGRwGyii+VR8GWExU41DRbyvLTQ@mail.gmail.com>
2019-07-20 23:30 ` unset TMP Variable issue Nikos Balkanas
2019-08-29 11:43 ` Cygcheck.out sent to list causes email to get blocked (was Re: unset TMP Variable issue) L A Walsh
2019-08-29 12:27 ` Nikos Balkanas
2019-08-30 1:42 ` 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=f9a4583e-5026-735f-c1de-7ecba802cd80@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).