From: D. Ben Knoble Date: Sun, 06 Sep 2026 13:30:26 GMT Subject: Re: What's cooking in git.git (Sep 2026, #02) Message-ID: In-Reply-To: On Sat, Sep 5, 2026 at 7:57 PM Junio C Hamano wrote: > > "D. Ben Knoble" writes: > > > On Fri, Sep 4, 2026 at 8:00 PM Junio C Hamano wrote: > >> * dk/use-nsec-runtime (2026-08-31) 3 commits > >> - core: convert build-time USE_NSEC into runtime core.useNanosec > >> - environment: align repo_config_values_init with struct declaration > >> - meson: expose knob for xmlto relative links in manuals > >> > >> The build-time knob 'USE_NSEC' for nanosecond stat precision has been > >> converted to a runtime configuration 'core.useNanosec', allowing > >> distributions to bundle one binary that adapts to filesystem > >> capabilities dynamically. > >> > >> Waiting for response. > >> cf. > >> source: > > > > Reply is at > > :) > > So, is > > A prior reply of mine to Patrick specifically mentioned diff > with submodules, I believe. But I agree that positive evidence > is probably better than negative evidence. > > in that message a sign that we should expect a reroll? > > Thanks. - From https://lore.kernel.org/git/an720tZnot07HYiK@pks.im/, we agreed to "hold this series hostage" over the_repository, I think - From https://lore.kernel.org/git/CALnO6CBejkZTgPM9tK6TEGeNYSRfi9r2-xi7R4ckTsRm4ZGaQw@mail.gmail.com/ (and replies), we don't currently have diff + recurse-submodules (though we do have --submodule, we don't think it uses in-process struct repository values). And in the message you quoted, I wrote next > All-in-all, I’m not inclined to change the shape of this series > at the present point in this discussion, but if you (or others) > feel strongly about this « safe default » being a requirement, > I will find some time eventually. So, I'm not planning on a reroll unless there's a strong demand for it? In particular, absent guidance for creating positive evidence of safety, which I've asked about a number of times, I'm not sure what more to do. -- D. Ben Knoble