zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Oliver Kiddle <opk@zsh.org>
Cc: Frank Terbeck <ft@zsh.org>, zsh-workers@zsh.org
Subject: Re: [PATCH] vcs_info: add 'find-deepest' zstyle
Date: Sun, 25 Oct 2020 19:54:01 +0000	[thread overview]
Message-ID: <20201025195401.3c54c6a2@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <37168-1603506679.130606@RR8o.26Eg.GGvC>

Oliver Kiddle wrote on Sat, 24 Oct 2020 04:31 +0200:
> Long detection times can still very much be a problem. At both home
> and work, I use automount and NFS home directories so the NFS server
> regularly gets queried for non-existent homes named .git etc. [...]
> 
> I suspect some of this could be avoided by doing something similar to
> the find -xdev option to stop searching when a different filesystem is
> reached.

So you'd like to assume that a single worktree will not cross into
nested mount points.

I'm not actually sure this is true every time.  For instance, if
a project's tree is huge and someone works only on part of it but has
multiple worktrees for that project, they might use bind mounts for the
parts of the tree they never touch; and conversely, people doing in-tree
builds might mount ramdisks inside their worktrees to generate the
object files and executables in, and then cd into those and expect to
still see the info for the enclosing worktree.

Whether any of these use-cases is a deal breaker is another question.

How about, if cwd is writable (in the access(W_OK) sense), stopping the
upwards crawl when reaching a directory that isn't writable?  This would
typically stop on «~/../».

> I don't have much use for nested repositories but vcs_info tends to be
> more use with git than subversion.

+1, primarily because git is much more stateful (e.g., interrupted
rebases).

Cheers,

Daniel


  reply	other threads:[~2020-10-25 19:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-23  8:34 Aleksandr Mezin
2020-10-23 23:48 ` Daniel Shahaf
2020-10-24  0:13   ` Frank Terbeck
2020-10-24  0:56     ` Bart Schaefer
2020-10-25 20:04       ` Daniel Shahaf
2020-10-24  2:31     ` Oliver Kiddle
2020-10-25 19:54       ` Daniel Shahaf [this message]
2020-10-25 23:13         ` Frank Terbeck
2020-10-26 20:58           ` Daniel Shahaf
2020-10-27  1:01             ` Frank Terbeck
2020-11-04  8:42               ` Daniel Shahaf
2020-10-28  1:33   ` Aleksandr Mezin

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=20201025195401.3c54c6a2@tarpaulin.shahaf.local2 \
    --to=d.s@daniel.shahaf.name \
    --cc=ft@zsh.org \
    --cc=opk@zsh.org \
    --cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).