From: Jose Isaias Cabrera <jicman@outlook.com>
To: Duncan Roe <duncan_roe@optusnet.com.au>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: bug with grep 3.0.2 in cygwin 3.0.7
Date: Fri, 30 Aug 2019 13:04:00 -0000 [thread overview]
Message-ID: <VI1PR01MB441354FBE3B4F9D9207BF10FDEBD0@VI1PR01MB4413.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <20190830074756.GB25467@dimstar.local.net>
Duncan Roe, on Friday, August 30, 2019 03:47 AM, wrote...
>
> On Thu, Aug 29, 2019 at 09:42:46PM -0400, Eliot Moss wrote:
> > On 8/29/2019 3:08 PM, Andrey Repin wrote:
> > But my main point is that RTM would be enough; RTFM seemed
> > to me perhaps a little more rude than necessary.
> >
> > Regards - EM
> >
> I don't see anything to object to in "Read The Fine Manual" ;)
You know real well what the F in RTFM stands for: Functioning. And that, my friend, is a little too much nowadays for them sensitivity unchallenged folks. Just my 102 Dominican cents. :-)
josé
--
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:[~2019-08-30 13:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1910922536.1217465852.1566975322390.JavaMail.root@zimbra76-e14.priv.proxad.net>
2019-08-28 8:32 ` akiki
2019-08-28 12:51 ` Eliot Moss
2019-08-28 13:33 ` Eric Blake
2019-08-29 19:20 ` Andrey Repin
2019-08-30 6:12 ` Eliot Moss
2019-08-30 7:48 ` Brian Inglis
2019-08-30 15:34 ` Eliot Moss
2019-08-30 7:50 ` Duncan Roe
2019-08-30 13:04 ` Jose Isaias Cabrera [this message]
2019-08-30 7:55 ` Andrey Repin
2019-09-23 14:42 ` Chris Wagner
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=VI1PR01MB441354FBE3B4F9D9207BF10FDEBD0@VI1PR01MB4413.eurprd01.prod.exchangelabs.com \
--to=jicman@outlook.com \
--cc=cygwin@cygwin.com \
--cc=duncan_roe@optusnet.com.au \
/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).