From: "Lars R. Damerow" <lars@pixar.com>
To: git@vger.kernel.org
Subject: [PATCH 2/2] Add support for GIT_ONE_FILESYSTEM
Date: Tue, 16 Mar 2010 15:05:01 -0700 [thread overview]
Message-ID: <1268777101-22122-3-git-send-email-lars@pixar.com> (raw)
In-Reply-To: <1268777101-22122-1-git-send-email-lars@pixar.com>
This patch makes git pay attention to the GIT_ONE_FILESYSTEM environment
variable. When that variable is set, git will stop searching for a
GIT_DIR when it attempts to cross a filesystem boundary.
When working in an environment with too many automount points to make
maintaining a GIT_CEILING_DIRECTORIES list enjoyable, GIT_ONE_FILESYSTEM
gives the option of turning all such attempts off with one setting.
Signed-off-by: Lars R. Damerow <lars@pixar.com>
---
Documentation/git.txt | 3 +++
setup.c | 17 ++++++++++++++++-
2 files changed, 19 insertions(+), 1 deletions(-)
diff --git a/Documentation/git.txt b/Documentation/git.txt
index 35c0c79..dbb590f 100644
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -529,6 +529,9 @@ git so take care if using Cogito etc.
a GIT_DIR set on the command line or in the environment.
(Useful for excluding slow-loading network directories.)
+'GIT_ONE_FILESYSTEM'::
+ Stop at filesystem boundaries when looking for .git or objects.
+
git Commits
~~~~~~~~~~~
'GIT_AUTHOR_NAME'::
diff --git a/setup.c b/setup.c
index 5716d90..d40e2e6 100644
--- a/setup.c
+++ b/setup.c
@@ -319,10 +319,12 @@ const char *setup_git_directory_gently(int *nongit_ok)
{
const char *work_tree_env = getenv(GIT_WORK_TREE_ENVIRONMENT);
const char *env_ceiling_dirs = getenv(CEILING_DIRECTORIES_ENVIRONMENT);
- static char cwd[PATH_MAX+1];
+ static char cwd[PATH_MAX+1], err_cwd[PATH_MAX+1];
const char *gitdirenv;
const char *gitfile_dir;
int len, offset, ceil_offset, root_len;
+ int current_device = 0, one_filesystem = 0;
+ struct stat buf;
/*
* Let's assume that we are in a git repository.
@@ -390,6 +392,11 @@ const char *setup_git_directory_gently(int *nongit_ok)
* etc.
*/
offset = len = strlen(cwd);
+ if ((one_filesystem = git_env_bool("GIT_ONE_FILESYSTEM", 0))) {
+ if (stat(".", &buf))
+ die_errno("failed to stat '.'");
+ current_device = buf.st_dev;
+ }
for (;;) {
gitfile_dir = read_gitfile_gently(DEFAULT_GIT_DIR_ENVIRONMENT);
if (gitfile_dir) {
@@ -422,6 +429,14 @@ const char *setup_git_directory_gently(int *nongit_ok)
}
die("Not a git repository (or any of the parent directories): %s", DEFAULT_GIT_DIR_ENVIRONMENT);
}
+ if (one_filesystem) {
+ if (stat("..", &buf))
+ die_errno("failed to stat '%s/..'", getcwd(err_cwd, sizeof(err_cwd)-1));
+ if (buf.st_dev != current_device)
+ die("Not a git repository (or any parent up to %s/..)\n"
+ "Stopping at filesystem boundary since GIT_ONE_FILESYSTEM is set.",
+ getcwd(err_cwd, sizeof(err_cwd)-1));
+ }
if (chdir(".."))
die_errno("Cannot change to '%s/..'", cwd);
}
--
1.6.5.2
next prev parent reply other threads:[~2010-03-16 22:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 22:04 [PATCH 0/2] Add support for GIT_ONE_FILESYSTEM (resubmission) Lars R. Damerow
2010-03-16 22:05 ` [PATCH 1/2] config.c: remove static keyword from git_env_bool() Lars R. Damerow
2010-03-16 22:05 ` Lars R. Damerow [this message]
2010-03-17 0:45 ` [PATCH 2/2] Add support for GIT_ONE_FILESYSTEM Nguyen Thai Ngoc Duy
2010-03-17 7:09 ` Johannes Sixt
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=1268777101-22122-3-git-send-email-lars@pixar.com \
--to=lars@pixar.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).