Thread (66 messages) flat view 66 messages, 5 authors, 3d ago

Re: [PATCH v6 0/3] Convert USE_NSEC to runtime config

From: D. Ben Knoble <hidden>
Date: 2026-08-31 20:06:28

Erm, woops

On Mon, Aug 31, 2026 at 4:02 PM D. Ben Knoble [off-list ref] wrote:
Topic name: dk/use-nsec-runtime (applied)

Topic summary: Expose USE_NSEC as a runtime configuration, since
build-time is too early for distributing Git [1]. As a result, common
index-related options, like git-diff, are less likely to hit "racy git"
problems on supported filesystems.

[1]: https://git.github.io/rev_news/2026/07/31/edition-137/

Built on master (2c78326f81 (The 11th batch, 2026-08-05)).
Changes in v6: slight comment tweak
Changes in v5:

- improve message flow in patch 2
[snip]
Diff-intervalle contre v5 :
1:  d612de6c2d = 1:  d612de6c2d meson: expose knob for xmlto relative links in manuals
2:  12974e07d0 = 2:  12974e07d0 environment: align repo_config_values_init with struct declaration
3:  01cd487cd2 ! 3:  0a611f6140 core: convert build-time USE_NSEC into runtime core.useNanosec
    @@ builtin/update-index.c: static void xrmdir(const char *path)
      {
        /*
     -   * not use if we could usleep(10) if USE_NSEC is defined. The
    -+   * not use if we could usleep(10) if core.useNanosec is defined. The
    ++   * not use if we could usleep(10) if core.useNanosec is enabled. The
         * field nsec could be there, but the OS could choose to
         * ignore it?
         */

base-commit: 2c78326f810173a4f3aefd8021f1e07575412481
--
2.55.0.860.g4b6b3295ed.dirty
Thanks

-- 
D. Ben Knoble
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help