From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Samuel Thibault <samuel.thibault@ens-lyon.org>
Subject: Re: [PATCH] Fix GNU/Hurd build
Date: Fri, 13 Mar 2026 07:39:40 +0100 [thread overview]
Message-ID: <abOxLFNGgZjo1dyi@pks.im> (raw)
In-Reply-To: <xmqqbjgsdbr6.fsf@gitster.g>
On Thu, Mar 12, 2026 at 01:38:21PM -0700, Junio C Hamano wrote:
> Samuel Thibault <samuel.thibault@ens-lyon.org> writes:
>
> > GNU/Hurd does not have a PATH_MAX limitation
>
> Thanks. clar folks might prefer to take it upstream and have us as
> a downstream to import from them, so I'll forward it first before
> taking it for ourselves.
>
> It makes me wonder if an organization like this is easier to follow,
> i.e., platform specific settings first and then catch-all default at
> the end:
>
> #if defined(CLAR_LONGPATHS)
> #define CLAR_MAX_PATH 4096
> #elif defined(PATH_MAX)
> #define CLAR_MAX_PATH PATH_MAX
> #elif deifned(MAX_PATH)
> #define CLAR_MAX_PATH MAX_PATH
> #fi
>
> #if !defined(CLAR_MAX_PATH)
> #define CLAR_MAX_PATH 4096
> #fi
>
> but that is a separate issue best handled by the clar folks.
Agreed, something like this would read better indeed. Samuel, do you
want to maybe create a pull request in [1] to fix this in clar itself?
You can then give me (@pks-gitlab) a ping and I'll be happy to review
it. I can then handle the subsequent pull request for Git.
Thanks!
Patrick
[1]: https://github.com/clar-test/clar
next prev parent reply other threads:[~2026-03-13 6:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 19:19 [PATCH] Fix GNU/Hurd build Samuel Thibault
2026-03-12 20:38 ` Junio C Hamano
2026-03-13 6:39 ` Patrick Steinhardt [this message]
2026-03-13 17:24 ` Samuel Thibault
2026-03-13 19:08 ` Junio C Hamano
2026-03-16 6:41 ` Patrick Steinhardt
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=abOxLFNGgZjo1dyi@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=samuel.thibault@ens-lyon.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