public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: mintty 2.9.9
Date: Thu, 28 Mar 2019 21:38:00 -0000	[thread overview]
Message-ID: <b7fa611b-a4a3-d6c6-27ac-b25eec1fa7fa@towo.net> (raw)
In-Reply-To: <87pnqa6asc.fsf@Rainer.invalid>

Am 28.03.2019 um 20:47 schrieb Achim Gratz:
> Thomas Wolff writes:
>> I do not like the dual chaos of manual vs info pages, and I'm maybe a
>> bit old-fashioned to insist that manual pages should be complete, but
>> isn't that their purpose?
> You are barking up the wrong tree, but if you're that bothered by it,
> you can file an RFE or bug report with upstream that you miss the
> "ENVIRONMENT VARIABLES" section on their man page.
Hi Achim, I didn't mean to bark, just to explain why I hadn't seen the 
TAR_OPTIONS, hope that's alright.

--
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

  reply	other threads:[~2019-03-28 21:38 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-16  9:35 Thomas Wolff
2019-03-16 14:01 ` Achim Gratz
2019-03-24 14:51   ` Steven Penny
2019-03-24 15:57   ` Thomas Wolff
2019-03-24 16:24     ` Brian Inglis
2019-03-24 18:19     ` Corinna Vinschen
2019-03-24 23:36       ` Thomas Wolff
2019-03-25  8:31         ` Corinna Vinschen
2019-03-25 18:12         ` Achim Gratz
2019-03-27 20:02           ` Thomas Wolff
2019-03-27 20:36             ` Achim Gratz
2019-03-27 21:01               ` Jeffrey Walton
2019-03-27 22:52             ` Steven Penny
2019-03-27 23:09               ` Yaakov Selkowitz
2019-03-28  1:12                 ` Steven Penny
2019-03-28  2:35                   ` Yaakov Selkowitz
2019-03-28  2:44                   ` Brian Inglis
2019-03-28  3:42                     ` Steven Penny
2019-03-28  7:34                       ` Thomas Wolff
2019-03-28 11:36                         ` Steven Penny
2019-03-28 15:09                           ` Brian Inglis
2019-03-28 18:22                           ` Dependancy Hell (was Re: [ANNOUNCEMENT] Updated: mintty 2.9.9) Chris Wagner
2019-03-28 17:37                         ` [ANNOUNCEMENT] Updated: mintty 2.9.9 Achim Gratz
2019-03-27 22:59             ` Yaakov Selkowitz
2019-03-28  7:15               ` Björn Stabel
2019-03-28 17:40                 ` Achim Gratz
2019-03-28 18:08                   ` Thomas Wolff
2019-03-28 18:21                     ` Achim Gratz
2019-03-28 18:32                       ` Thomas Wolff
2019-03-28 19:47                         ` Achim Gratz
2019-03-28 21:38                           ` Thomas Wolff [this message]
2019-03-28  8:43               ` Thomas Wolff
2019-03-28  9:36                 ` Corinna Vinschen
2019-03-28 14:02                 ` Jeffrey Walton
2019-03-28 18:10                   ` Thomas Wolff
2019-03-28 18:16                     ` Vince Rice
2019-03-28 18:33                       ` Thomas Wolff
2019-03-28 18:43                         ` Vince Rice
2019-03-28 21:34                           ` Thomas Wolff
2019-03-28 22:28                             ` Steven Penny
2019-03-24 21:05     ` Andrey Repin

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=b7fa611b-a4a3-d6c6-27ac-b25eec1fa7fa@towo.net \
    --to=towo@towo.net \
    --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).