From: Junio C Hamano <gitster@pobox.com>
To: Gatla Vishweshwar Reddy <gatlavishweshwarreddy26@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] setup.c: use die_errno() when chdir() system call fails
Date: Mon, 06 Jul 2026 12:35:37 -0700 [thread overview]
Message-ID: <xmqqbjcjc3na.fsf@gitster.g> (raw)
In-Reply-To: <20260706183851.90517-1-gatlavishweshwarreddy26@gmail.com> (Gatla Vishweshwar Reddy's message of "Tue, 7 Jul 2026 00:08:51 +0530")
Gatla Vishweshwar Reddy <gatlavishweshwarreddy26@gmail.com> writes:
> ---
The usual way to compose a log message (i.e., what the readers would
have seen above that three-dash line we see) of this project is to
- Give an observation on how the current system works in the
present tense (so no need to say "Currently X is Y", or
"Previously X was Y" to describe the state before your change;
just "X is Y" is enough), and discuss what you perceive as a
problem in it.
- Propose a solution (optional---often, problem description
trivially leads to an obvious solution in reader's minds).
- Give commands to somebody editing the codebase to "make it so",
instead of saying "This commit does X".
in this order. And then to conclude the message, add your sign-off
(see Documentation/SubmittingPatches:[[sign-off]]).
> setup.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
The changes are trivially correct, in that you call die_errno()
immediately after seeing chdir() fail (which means there is no other
potential failures that can contaminate errno---what your die_errno()
will report cannot be anything but what we got from chdir()).
> diff --git a/setup.c b/setup.c
> index b4652651df..e2e98d1126 100644
> --- a/setup.c
> +++ b/setup.c
> @@ -1954,13 +1954,13 @@ const char *setup_git_directory_gently(struct repository *repo, int *nongit_ok)
> break;
> case GIT_DIR_DISCOVERED:
> if (dir.len < cwd.len && chdir(dir.buf))
> - die(_("cannot change to '%s'"), dir.buf);
> + die_errno(_("cannot change to '%s'"), dir.buf);
> prefix = setup_discovered_git_dir(repo, gitdir.buf, &cwd, dir.len,
> &repo_fmt, nongit_ok);
> break;
> case GIT_DIR_BARE:
> if (dir.len < cwd.len && chdir(dir.buf))
> - die(_("cannot change to '%s'"), dir.buf);
> + die_errno(_("cannot change to '%s'"), dir.buf);
> prefix = setup_bare_git_dir(repo, &cwd, dir.len, &repo_fmt, nongit_ok);
> break;
> case GIT_DIR_HIT_CEILING:
prev parent reply other threads:[~2026-07-06 19:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 18:38 [PATCH] setup.c: use die_errno() when chdir() system call fails Gatla Vishweshwar Reddy
2026-07-06 19:35 ` Junio C Hamano [this message]
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=xmqqbjcjc3na.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=gatlavishweshwarreddy26@gmail.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