From: "Dirk Süsserott" <newsletter@dirk.my1.cc>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Carlos Martín Nieto" <carlos@cmartin.tk>,
"Massimo Manca" <massimo.manca@micronengineering.it>,
git@vger.kernel.org
Subject: Re: git bash
Date: Mon, 18 Jul 2011 20:51:41 +0200 [thread overview]
Message-ID: <4E2480BD.9000403@dirk.my1.cc> (raw)
In-Reply-To: <alpine.DEB.1.00.1107150114240.2642@bonsai2>
Hi Johannes,
Am 15.07.2011 01:15 schrieb Johannes Schindelin:
> Hi Dirk,
>
> On Fri, 17 Jun 2011, Dirk Süsserott wrote:
>
>> I noticed the following: When the ext. HD is attached/mounted *before* I
>> start the bash, then it works. But if I have a running bash and then
>> mount the drive, I cannot cd to it. "No such path" or sth. It seems,
>> that bash builds a list of available drives only at startup. Might that
>> be your problem? If so, then close all bashs and re-open them after
>> mounting the devices.
>
> This behavior is discussed here:
>
> http://permalink.gmane.org/gmane.comp.version-control.git/141867
>
> (look for "NO_FSTAB_THREAD")
>
> Ciao,
> Johannes
thank you for the pointer. That's what I've observed. To be honest, I'm
one of the lazy guys and didn't really understand the impact of setting
NO_FSTAB_THREAD at first glance. As I understood, setting it means
"mounting drives afterwards works, but slows things down" and not
setting it means the opposite. Meanwhile I'm familiar with re-starting
my git-bash in case (that's not too bad for me). I almost never run git
commands from cmd.exe because cmd.exe is rubbish.
But, again, thanx for the help; now I know how to fine-tune the
behaviour if I wish.
Cheers,
Dirk
prev parent reply other threads:[~2011-07-18 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 13:52 git bash Massimo Manca
2011-06-17 14:18 ` Carlos Martín Nieto
2011-06-17 14:39 ` Dirk Süsserott
2011-06-17 15:07 ` Massimo Manca
2011-07-14 23:15 ` Johannes Schindelin
2011-07-18 18:51 ` Dirk Süsserott [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=4E2480BD.9000403@dirk.my1.cc \
--to=newsletter@dirk.my1.cc \
--cc=Johannes.Schindelin@gmx.de \
--cc=carlos@cmartin.tk \
--cc=git@vger.kernel.org \
--cc=massimo.manca@micronengineering.it \
/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 NNTP newsgroup(s).