From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Subject: Re: Git status delay
Date: Mon, 11 Dec 2017 21:38:00 -0000 [thread overview]
Message-ID: <20171211211047.GA27961@dinwoodie.org> (raw)
In-Reply-To: <184959217.20171211143738@volny.cz>
On Monday 11 December 2017 at 02:37 pm +0100, Dawid Ferenczy wrote:
> You can see that it hanged for about 30 seconds trying to open the file
> "\\HEAD\PIPE\wkssvc" which obviously failed with the BAD NETWORK PATH error.
> On my system, it always hangs for the same amount time, it's most likely a
> timeout.
Hi Dawid,
So I can look into this, I need the information I asked for in the email
you replied to. To repeat, that's:
> - The cygcheck output per the bolded bullet in the problem reporting
> guidelines: http://cygwin.com/problems.html.
>
> - The version of Git you're running, per `git --version`, if it hasn't
> been installed using Cygwin's setup-*.exe installers.
>
> - The current working directory when you run `git status`.
>
> - Details of the directory structure of the repository you're running
> `git status` in. I'm mainly after where the `.git` directory is in
> relation to the current working directory, but if there's anything
> else that's not entirely standard I'd like to know that, too (e.g. it
> being a bare repository).
>
> - Whether you're running Bash in MinTTY, Windows cmd shell, or something
> else.
>
> - If there's anything special about your shell prompt (e.g. you're using
> one of the git prompt tools to include repository status summaries in
> your shell prompt).
You've included some of that information in your reply, but I do need it
all to be able to look at this.
Also, per the mailing list notes at <https://cygwin.com/lists.html>,
please configure your mailer to not include people's email addresses in
your replies.
Cheers,
Adam
--
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:[~2017-12-11 21:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-18 21:13 Richard H Lee
2017-11-20 10:04 ` Richard H Lee
2017-11-20 14:33 ` cyg Simple
2017-11-20 17:05 ` Andrey Repin
2017-11-21 10:27 ` Adam Dinwoodie
2017-12-05 14:14 ` Dawid Ferenczy
2017-12-05 17:00 ` Dawid Ferenczy
2017-12-11 23:36 ` Richard H Lee
2017-12-12 16:41 ` cyg Simple
2017-12-11 17:19 ` Dawid Ferenczy
2017-12-11 21:38 ` Adam Dinwoodie [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=20171211211047.GA27961@dinwoodie.org \
--to=adam@dinwoodie.org \
--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).