From: Martin Atukunda <matlads@dsmagic.com>
To: git@vger.kernel.org
Cc: Martin Atukunda <matlads@dsmagic.com>
Subject: [PATCH 4/6] Add check_repo_format check for all major operations.
Date: Tue, 22 Nov 2005 03:28:13 +0300 [thread overview]
Message-ID: <113261929333-git-send-email-matlads@dsmagic.com> (raw)
In-Reply-To: <11326192921291-git-send-email-matlads@dsmagic.com>
The git-* command set uses 3 entry points in order to prepare
to work with a git repo: enter_repo, get_git_dir, and obviously
setup_git_directory.
This patch adds a check for the repo format version to each of these
entry points. This will automatically enable repo format version
checking for all the git-* programs.
Signed-Off-By: Martin Atukunda <matlads@dsmagic.com>
---
environment.c | 3 +++
path.c | 1 +
setup.c | 3 +++
3 files changed, 7 insertions(+), 0 deletions(-)
applies-to: 8084b72bfb91efc08a9fa83e0893f21c5f60ad92
5d902692ef7eef2763cadfa646eb9245422579af
diff --git a/environment.c b/environment.c
index 6a961ca..458eff8 100644
--- a/environment.c
+++ b/environment.c
@@ -37,6 +37,9 @@ static void setup_git_env(void)
git_graft_file = getenv(GRAFT_ENVIRONMENT);
if (!git_graft_file)
git_graft_file = strdup(git_path("info/grafts"));
+
+ /* check the repo */
+ check_repo_format();
}
char *get_git_dir(int recheck_env)
diff --git a/path.c b/path.c
index e322dc0..84cb1c5 100644
--- a/path.c
+++ b/path.c
@@ -199,6 +199,7 @@ char *enter_repo(char *path, int strict)
if(access("objects", X_OK) == 0 && access("refs", X_OK) == 0 &&
validate_symref("HEAD") == 0) {
putenv("GIT_DIR=.");
+ get_git_dir(1); /* re-read the env variables */
return current_dir();
}
diff --git a/setup.c b/setup.c
index 8597424..934f9a3 100644
--- a/setup.c
+++ b/setup.c
@@ -97,6 +97,9 @@ const char *setup_git_directory(void)
static char cwd[PATH_MAX+1];
int len, offset;
+ get_git_dir(1);
+ check_repo_format();
+
/*
* If GIT_DIR is set explicitly, we're not going
* to do any discovery
---
0.99.9.GIT
next prev parent reply other threads:[~2005-11-22 0:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 0:28 Git Future Proofing Martin Atukunda
2005-11-22 0:28 ` [PATCH 2/6] Make init-db check repo format version if copying a config file Martin Atukunda
2005-11-22 0:28 ` [PATCH 3/6] Make get_git_dir take a flag that makes it re-read the env. variables Martin Atukunda
2005-11-22 0:28 ` [PATCH 1/6] Add GIT_REPO_VERSION, and repository_format_version Martin Atukunda
2005-11-22 0:28 ` [PATCH 5/6] Allow Specification of the conf file to read for git_config operations Martin Atukunda
2005-11-22 0:28 ` Martin Atukunda [this message]
2005-11-22 8:29 ` [PATCH 4/6] Add check_repo_format check for all major operations Junio C Hamano
2005-11-22 12:55 ` Martin Atukunda
2005-11-22 17:46 ` Junio C Hamano
2005-11-23 0:57 ` Junio C Hamano
2005-11-22 0:28 ` [PATCH 6/6] Add check for downgrading of repo format version via init-db Martin Atukunda
2005-11-22 1:13 ` Git Future Proofing Junio C Hamano
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=113261929333-git-send-email-matlads@dsmagic.com \
--to=matlads@dsmagic.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).