From: Thomas Rast <trast@student.ethz.ch>
To: Cesar Crusius <cesar@cariden.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [BUG] Using git-completion with automounted home directories causes bogus NFS mount requests
Date: Thu, 17 Jun 2010 22:02:54 +0200 [thread overview]
Message-ID: <201006172202.54879.trast@student.ethz.ch> (raw)
In-Reply-To: <B0356A858DE69744B8977A67332BFB2C1FE9CDAD@dc1.mv.cariden.com>
Cesar Crusius wrote:
> Hi all,
>
> I have tried this with various versions of .git-completion,
> including the most recent one as of today, and whenever I have
> __git_ps1 in my bash prompt, I get messages like this:
>
> Jun 17 12:05:14 sunray automountd[471]: [ID 834250 daemon.error] Mount of <server>:/export/home/.git on /home/.git: No such file or directory
[...]
> This is probably a result of git/git-completion trying to access the
> directories above, and automount trying to get them from the server
> (we're in an NFS home environment, with wildcard automounts in
> auto_home).
It's not a bug. Git repositories have only one .git metadata
directory at the root of the repo. How could git possibly detect
where the repository is, if not by scanning each directory up to the
root for a .git entry?
For a workaround, set GIT_CEILING_DIRECTORIES (available since 1.6.0),
see git(1). The next released version will most likely default to not
searching across mount points thanks to commit 8030e44 (Add support
for GIT_ONE_FILESYSTEM, 2010-03-17).
--
Thomas Rast
trast@{inf,student}.ethz.ch
prev parent reply other threads:[~2010-06-17 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 19:32 [BUG] Using git-completion with automounted home directories causes bogus NFS mount requests Cesar Crusius
2010-06-17 20:02 ` Thomas Rast [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=201006172202.54879.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=cesar@cariden.com \
--cc=git@vger.kernel.org \
/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).