public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Cc: engr.sidrahijaz@gmail.com
Subject: Re: Error
Date: Mon, 22 Oct 2018 18:42:00 -0000	[thread overview]
Message-ID: <57b79266-f504-e2d3-1b4a-01a4cdc4c533@gmail.com> (raw)
In-Reply-To: <67d29328-0d82-7a0c-4680-a64c77eac71a@mail.com>

Am 22.10.2018 um 18:46 schrieb john doe:
> On 10/22/2018 6:32 PM, sidrah ijaz wrote:
>> could not compute FAST_CWD pointer
>>
>
> Not sure if the above is a question.
>
> https://cygwin.com/faq/faq.html#faq.using.fixing-find_fast_cwd-warnings
>
> HTH.
>

Joe,
It is. Adding original sender in copy.

Sidrah,
your mail is a record of short length.
If this was real problem and you were asking support you are supposed
to provide much more info than just copy the error message.
Have you thought that an error message can be shared by hundred of
application and to help you anyone should receive some informations ?
Or you think a customer support will magically know the details
of your problem that you missed to provide ?

In this case our faq explain the matter
https://cygwin.com/faq/faq.html#faq.using.fixing-find_fast_cwd-warnings

and you can report the issue to whoever is distributing the software
you are using.

Regards
Marco



---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


--
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-10-22 18:42 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-22 16:32 Error sidrah ijaz
2018-10-22 16:47 ` Error john doe
2018-10-22 18:42   ` Marco Atzeri [this message]
     [not found] <15465410-431f-7742-157e-25cc52d8f67e.ref@aol.com>
2023-08-21 13:18 ` Error Rich Kent
2023-08-21 13:21   ` Error cygwinautoreply
  -- strict thread matches above, loose matches on Subject: below --
2020-02-10 18:06 Error Qasim Imtiaz
2020-02-10 18:07 ` Error cygwinautoreply
     [not found] <1589861088.3980868.1558121342585.ref@mail.yahoo.com>
2019-05-17 19:31 ` error Donatas N. via cygwin
2019-05-17 19:33   ` error cygwinautoreply
2018-07-31 16:27 Error Medina, Adela
2018-07-31 17:57 ` Error Andrey Repin
2018-08-03  5:55   ` Error steve shepard
2018-05-05 18:10 Error Maxime M
2018-03-23 21:18 error Arthur Philippi Bianco
2018-03-23 22:28 ` error Marco Atzeri
2018-03-06 15:39 Error Sagar jack
2018-03-06 17:43 ` Error Marco Atzeri
     [not found] <176560894.1079324.1513687602434.ref@mail.yahoo.com>
2017-12-19 14:35 ` Error Joe Nayo via cygwin
     [not found] <427349927.417716.1513595594671.ref@mail.yahoo.com>
2017-12-18 11:29 ` Error Joe Nayo via cygwin
2017-12-18 11:35   ` Error Markus Schönhaber
2017-12-19  8:38     ` Error Marco Atzeri
2017-10-26 17:46 error Spectre.nb1 Spectre.nb1
2014-12-16  2:04 error august224
2014-12-16  2:08 ` error Larry Hall (Cygwin)
     [not found] <667059605.426228.1414530635980.JavaMail.root@louisiana.edu>
2014-10-28 22:26 ` Error Elizabeth M Theriot
2014-10-28 22:50   ` Error Larry Hall (Cygwin)
2014-10-29 13:26     ` Error Douglas Coup
2001-09-27 17:17 Error frank fuller
2001-09-28  0:45 ` Error Pavel Tsekov

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=57b79266-f504-e2d3-1b4a-01a4cdc4c533@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=engr.sidrahijaz@gmail.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).