public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Problem
Date: Tue, 01 May 2018 05:10:00 -0000	[thread overview]
Message-ID: <b09c5a9c-6e74-3089-e4a9-d30a6efd01e2@SystematicSw.ab.ca> (raw)
In-Reply-To: <CACoZoo3EkLtZWwfksFAS6GWGp6PYsMtBB0S2zdQyXYiSORBO0Q@mail.gmail.com>

On 2018-04-30 18:25, Erik Soderquist wrote:
> On Mon, Apr 30, 2018 at 5:55 PM, Yaakov Selkowitz wrote:
>> On 2018-04-30 15:52, Ariel prro wrote:
>>> Hello, im having a problem with one program in my PC, it says couldn't
>>> compute CWD_FAST pointer, and to report it to you, can you help me
>>> please?
>> https://cygwin.com/faq/faq.html#faq.using.fixing-find_fast_cwd-warnings
> At this point I'm kind of wishing the embedded message pointed to
> http://cygwin.com/problems.html rather than the mailing list...

Perhaps the embedded message could now reference the FAQ entry, although most
posts contain the original message from years ago, which could possibly be
auto-replied to by sourceware?

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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:[~2018-05-01  5:10 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-30 20:52 Problem Ariel prro
2018-04-30 21:55 ` Problem Yaakov Selkowitz
2018-05-01  0:25   ` Problem Erik Soderquist
2018-05-01  5:10     ` Brian Inglis [this message]
2018-05-01 10:33     ` Problem Achim Gratz
     [not found] <888204452.186848.1640862891443.ref@mail.yahoo.com>
2021-12-30 11:14 ` Problem Carlos Rodríguez
2021-12-30 11:17   ` Problem cygwinautoreply
  -- strict thread matches above, loose matches on Subject: below --
2021-06-09  1:29 problem Serendipity
2021-06-09  3:34 ` problem Russell VT
2021-06-09  5:01 ` problem cygwinautoreply
2014-04-27  9:36 problem Farrokh Razavi
2014-04-27 11:28 ` problem Adam Dinwoodie
2014-04-28 13:50 ` problem Douglas Coup
2014-02-18 14:21 problem Brian Holley
2014-02-18 14:27 ` problem Corinna Vinschen
2014-02-24 13:37   ` problem Cristi
2014-02-24 15:17     ` problem Corinna Vinschen
2014-02-24 15:42       ` problem Corinna Vinschen
2011-08-13 21:00 Problem John Dzielski
2011-08-15 16:57 ` Problem Larry Hall (Cygwin)
2011-08-15 17:03   ` Problem John Dzielski
2011-08-15 17:09     ` Problem Larry Hall (Cygwin)
2005-10-17 21:23 Problem gmehl
2005-10-17 21:45 ` Problem Larry Hall (Cygwin)
2005-10-18  2:19 ` Problem Eric Blake
2004-12-21 12:30 problem Duch
2004-12-21 14:18 ` problem Rob S.i.k.l.o.s
2004-12-21 18:12   ` problem Larry Hall
2004-12-21 14:51 ` problem Igor Pechtchanski
2001-12-19 11:48 Problem Sasa Scrobogna
2001-11-16  7:57 problem fd ijhiujh
2001-11-26 17:13 ` problem fd ijhiujh
2001-05-23  4:47 problem Sarah Shannon
2001-05-23 12:17 ` problem Michael A. Chase
2000-06-03 18:29 Problem Todd Pace
1999-08-15 11:15 problem Earnie Boyd
1999-08-31 23:49 ` problem Earnie Boyd
1999-08-15  7:56 problem MadMojoBug
1999-08-31 23:49 ` problem MadMojoBug

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=b09c5a9c-6e74-3089-e4a9-d30a6efd01e2@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).