From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git mailing list <git@vger.kernel.org>,
Karthik Nayak <karthik.188@gmail.com>
Subject: Re: [RFC PATCH 2/3] setup: introduce new helper 'is_git_directory_verbose'
Date: Fri, 25 Sep 2026 23:21:08 +0530 [thread overview]
Message-ID: <c7808d4b-36f8-4583-8836-7b7d8bc24905@gmail.com> (raw)
In-Reply-To: <xmqqcxu2z4cy.fsf@gitster.g>
On 9/25/26 03:41, Junio C Hamano wrote:
> Kaartic Sivaraam <kaartic.sivaraam@gmail.com> writes:
>
>> diff --git a/setup.c b/setup.c
>> index 0d157ac254..b3b53a1cfc 100644
>>
>> /* Make sure it is a "refs/.." symlink */
>> if (S_ISLNK(st.st_mode)) {
>> len = readlink(path, buffer, sizeof(buffer)-1);
>> if (len >= 5 && !memcmp("refs/", buffer, 5))
>> return 0;
>> + if (len == -1 && err)
>> + strbuf_addf(
>> + err,
>> + _("could not read the symlink HEAD at '%s'"),
>> + path
>> + );
>> + else if (err)
>> + strbuf_addf(
>> + err,
>> + _("HEAD is a symlink ('%s') but target"
>> + " lives outside refs/"),
>> + path
>> + );
>> return -1;
>> }
>
> All of the above (and below---ellided) look fairly funny way to
> indent them. If you are trying ot match the style used in the
> existing code around the same area, I wouldn't complain, but I
> didn't look beyond what is visible in the patch.
>
Indeed. My bad. Does the following look like a good indentation style
for shorter messages?
if (lstat(path, &st) < 0) {
if (err)
strbuf_addf(err, _("could not stat HEAD at '%s'"), path);
return -1;
}
... and this for messages that are a bit longer:
if (len == -1 && err)
strbuf_addf(err, _("could not read the symlink HEAD at '%s'"),
path);
else if (err)
strbuf_addf(err, _("HEAD is a symlink ('%s') but target lives"
" outside refs/"), path);
--
Sivaraam
PS: I'm not yet very sure if my MUA will send this as intended. Will
resend if it doesn't. Excuse the noise in advance.
next prev parent reply other threads:[~2026-09-25 17:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 12:02 [RFC PATCH 0/3] Improve error reporting to mention "why" a directory is not a repository Kaartic Sivaraam
2026-09-24 12:02 ` [RFC PATCH 1/3] t0009: add tests to cover more error reporting scenarios Kaartic Sivaraam
2026-09-24 22:08 ` Junio C Hamano
2026-09-25 13:46 ` Kaartic Sivaraam
2026-09-24 12:02 ` [RFC PATCH 2/3] setup: introduce new helper 'is_git_directory_verbose' Kaartic Sivaraam
2026-09-24 22:11 ` Junio C Hamano
2026-09-25 17:51 ` Kaartic Sivaraam [this message]
2026-09-24 12:02 ` [RFC PATCH 3/3] setup: communicate why a directory is not a valid git directory Kaartic Sivaraam
2026-09-24 22:16 ` Junio C Hamano
2026-09-25 14:33 ` Kaartic Sivaraam
2026-09-29 10:25 ` [RFC PATCH v2 0/4] Improve error reporting to mention "why" a directory is not a repository Kaartic Sivaraam
2026-09-29 10:25 ` [RFC PATCH v2 1/4] setup: normalize an if-else to follow our convention Kaartic Sivaraam
2026-09-29 10:25 ` [RFC PATCH v2 2/4] t0009: add tests to cover more error reporting scenarios Kaartic Sivaraam
2026-09-29 10:25 ` [RFC PATCH v2 3/4] setup: introduce new helper 'is_git_directory_verbose' Kaartic Sivaraam
2026-09-30 16:03 ` Patrick Steinhardt
2026-10-05 12:14 ` Kaartic Sivaraam
2026-09-30 18:32 ` Junio C Hamano
2026-09-29 10:25 ` [RFC PATCH v2 4/4] setup: communicate why a directory is not a valid git directory Kaartic Sivaraam
2026-09-30 16:03 ` Patrick Steinhardt
2026-10-05 12:29 ` Kaartic Sivaraam
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=c7808d4b-36f8-4583-8836-7b7d8bc24905@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=karthik.188@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.