From: Junio C Hamano <junkio@cox.net>
To: Martin Atukunda <matlads@dsmagic.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 4/6] Add check_repo_format check for all major operations.
Date: Tue, 22 Nov 2005 00:29:29 -0800 [thread overview]
Message-ID: <7vlkzhf5li.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <113261929333-git-send-email-matlads@dsmagic.com> (Martin Atukunda's message of "Tue, 22 Nov 2005 03:28:13 +0300")
Martin Atukunda <matlads@dsmagic.com> writes:
> 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.
Thanks, but I think this one is wrong.
> 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();
> }
> 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
In setup_git_env() you have only read GIT_DIR environment but
have not done the toplevel discovery. Especially, this is
called from get_git_dir(), and you call that as the first thing
as setup_git_directory(). However, that function is supposed to
be callable by processes that are in a subdirectory, without
GIT_DIR explicitly specified, and the place get_git_dir() is
called in that function is way before the discovery of the
toplevel happens. Until then, you do not know where your .git/
directory or .git/config file is. If you start in Documentation
subdirectory in git project, your setup_git_directory() would
first call get_git_dir(), which says "I assume the config file
is at ./.git/config -- oh there is no such thing". At that
point you are checking Documentation/.git/config.
It would happen to work because you intend to allow version 0
repository for any future version of tool, and even if this
codepath mistakenly thinks the repository is version 0, it does
not hurt, as long as your setup_git_directory() calls
check_repo_format again after doing the toplevel discovery and
checks the true .git/config file, but I do not think you have
that call in the current series yet. Even if you had, this does
not feel quite right to me.
next prev parent reply other threads:[~2005-11-22 8:29 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 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 2/6] Make init-db check repo format version if copying a config file 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 ` [PATCH 6/6] Add check for downgrading of repo format version via init-db Martin Atukunda
2005-11-22 0:28 ` [PATCH 4/6] Add check_repo_format check for all major operations Martin Atukunda
2005-11-22 8:29 ` Junio C Hamano [this message]
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 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=7vlkzhf5li.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=matlads@dsmagic.com \
/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).