git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (Sep 2026, #02)

From
D. Ben Knoble <ben.knoble@gmail.com>
Date
Sep 6, 2026, 13:30 UTC
Message-ID
<CALnO6CDy-tLA4aN0-btkvS472RT5BCvE2xshp1-MekcO7v-wbQ@mail.gmail.com>
In-Reply-To
<xmqqa4pv5k1e.fsf@gitster.g>
On Sat, Sep 5, 2026 at 7:57 PM Junio C Hamano <gitster@pobox.com> wrote:
Show 30 quoted lines
>
> "D. Ben Knoble" <ben.knoble@gmail.com> writes:
>
> > On Fri, Sep 4, 2026 at 8:00 PM Junio C Hamano <gitster@pobox.com> 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. <xmqqbjaefhwo.fsf@gitster.g>
> >>  source: <cover.1788206466.git.ben.knoble@gmail.com>
> >
> > Reply is at <https://lore.kernel.org/git/D0BA1B32-1CAD-4328-A612-75A648413017@gmail.com/>
> > :)
>
> 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
Previous: Junio C Hamano
Message 7 of 7 in “What's cooking in git.git (Sep 2026, #02)”
  1. Junio C HamanoSep 4, 2026
  2. kh/doc-datamodelKristoffer Haugsbakk, Sep 5, 2026
  3. Junio C HamanoSep 5, 2026
  4. kh/format-patch-range-diff-notesKristoffer Haugsbakk, Sep 5, 2026
  5. D. Ben KnobleSep 5, 2026
  6. Junio C HamanoSep 5, 2026
  7. D. Ben KnobleSep 6, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.