From: Junio C Hamano <gitster@pobox.com>
To: Lidong Yan <yldhome2d2@gmail.com>
Cc: git@vger.kernel.org, christian.couder@gmail.com,
shyamthakkar001@gmail.com, ayu.chandekar@gmail.com,
Lidong Yan <502024330056@smail.nju.edu.cn>
Subject: Re: [PATCH] git.c: remove the_repository dependence in run_builtin()
Date: Thu, 12 Jun 2025 10:16:15 -0700 [thread overview]
Message-ID: <xmqqecvoev8g.fsf@gitster.g> (raw)
In-Reply-To: <20250612045905.3023227-1-502024330056@smail.nju.edu.cn> (Lidong Yan's message of "Thu, 12 Jun 2025 12:59:05 +0800")
Lidong Yan <yldhome2d2@gmail.com> writes:
> run_builtin() takes a repo parameter, so the use of the_repository
> is no longer necessary. Removed the usage of the_repository.
Good. The caller always calls this function with the_repository, so
this patch does not change anything in the bigger picture.
> The comment before trace_repo_setup() advises not to use get_git_dir(),
> but this note is unrelated to trace_repo_setup() itself. Additionally,
> get_git_dir() has now been renamed to repo_get_git_dir(). Remove this
> comment line.
Isn't it still relevant to explain the reason why this codepath
avoids calling the repo_get_git_dir() function?
e5b17bda (git: ensure correct git directory setup with -h,
2021-12-06) tells us that the comment is about use of
startup_info->have_repository, which was added by a9ca8a85
(builtins: print setup info if repo is found, 2010-11-26).
> Signed-off-by: Lidong Yan <502024330056@smail.nju.edu.cn>
> ---
> git.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/git.c b/git.c
> index 77c4359522..429ad1c2fb 100644
> --- a/git.c
> +++ b/git.c
> @@ -462,12 +462,11 @@ static int run_builtin(struct cmd_struct *p, int argc, const char **argv, struct
> precompose_argv_prefix(argc, argv, NULL);
> if (use_pager == -1 && run_setup &&
> !(p->option & DELAY_PAGER_CONFIG))
> - use_pager = check_pager_config(the_repository, p->cmd);
> + use_pager = check_pager_config(repo, p->cmd);
> if (use_pager == -1 && p->option & USE_PAGER)
> use_pager = 1;
> if (run_setup && startup_info->have_repository)
> - /* get_git_dir() may set up repo, avoid that */
> - trace_repo_setup(the_repository);
> + trace_repo_setup(repo);
> commit_pager_choice();
>
> if (!help && p->option & NEED_WORK_TREE)
next prev parent reply other threads:[~2025-06-12 17:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 4:59 [PATCH] git.c: remove the_repository dependence in run_builtin() Lidong Yan
2025-06-12 17:16 ` Junio C Hamano [this message]
2025-06-13 1:53 ` lidongyan
2025-06-13 4:49 ` Junio C Hamano
2025-06-14 5:03 ` [PATCH v2] " Lidong Yan
2025-06-14 23:35 ` Junio C Hamano
2025-06-15 1:49 ` Lidong Yan
2025-06-16 0:53 ` Junio C Hamano
2025-06-16 5:36 ` Lidong Yan
2025-06-16 5:41 ` Junio C Hamano
2025-06-15 14:46 ` [RFC PATCH v3 0/2] small fixes for git.c and setup.c Lidong Yan
2025-06-15 14:46 ` [PATCH v3 1/2] git.c: remove the_repository dependence in run_builtin() Lidong Yan
2025-06-15 14:46 ` [PATCH v3 2/2] setup: fix NEEDSWORK in setup_git_directory_gently() Lidong Yan
2025-06-16 1:25 ` [RFC PATCH v3 0/2] small fixes for git.c and setup.c Junio C Hamano
2025-06-16 1:36 ` Lidong Yan
2025-06-16 6:22 ` [PATCH v4] git.c: remove the_repository dependence in run_builtin() Lidong Yan
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=xmqqecvoev8g.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=502024330056@smail.nju.edu.cn \
--cc=ayu.chandekar@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=shyamthakkar001@gmail.com \
--cc=yldhome2d2@gmail.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