Skip to content
HN On Hacker News ↗

OpenAI Git · patches & notes

▲ 9 points • by fratellobigio • 3mo ago • HN discussion ↗

Pangram verdict · v3.3

We believe that this text is a mix of AI and human-written content.

62 %

AI likelihood · overall

AI
11% human-written 89% AI-generated
SEGMENTS · HUMAN 0 of 3
SEGMENTS · AI 0 of 3
WORD COUNT 385
PEAK AI % 61% · §2
Analyzed
Aug 1
backend: pangram/v3.3
Segments scanned
3 windows
avg 128 words each
Distribution
11 / 89%
human / AI fraction
Verdict
AI
Pangram v3.3

Article text · 385 words · 3 segments analyzed

Human AI-generated
§1 Mixed · 48%

Upstream statusmaster2 threadsAlready merged into upstream Git's master branch.FromTed NymanDate20 Jul 2026Commit1be6ebe26403Patches2A path-limited git stash expanded the full sparse index even when every requested path was already inside the sparse checkout.Keep the index sparse when possible, expand it when a pathspec needs the full index, and fix a related out-of-bounds read. Paths outside the sparse-checkout cone retain their existing behavior.18.87 s four index expansions 0.06 s zero index expansionsFromTaylor BlauDate21 Jun 2026Commit7e6de2ac6281Patches4Path-based pack traversal could not use reachability bitmaps or delta islands.Enable both existing pack optimizations during path-walk by collecting commit and tree information from its existing callback.

§2 Mixed · 61%

Fall back to ordinary traversal when a bitmap cannot satisfy the request.Upstream statusseen5 threadsIn upstream seen and still under review.FromTed NymanDate26 Jul 2026Commitc4244bdfe6d2Patches6Concurrent pack downloads could corrupt a partial pack, race cleanup, or mishandle a completed resume.Write each download at the correct offset, keep the pack available for indexing, and handle completed downloads. Accept an existing keep file only when its pack hash matches the advertised value.FromTaylor BlauDate24 Jul 2026Commitfd2739b159d0Patches5Duplicate objects in a pack could confuse reverse indexes, multi-pack indexes, and bitmap reuse.Match objects to their actual pack offsets, recover usable copies when resolving deltas, and avoid unsafe bitmap reuse. Fall back to ordinary packing when a selected index entry does not match its physical pack position.FromTaylor BlauDate12 Jul 2026Commit90202ce6e1daPatches4Some Git servers cannot accept REF_DELTA objects, but clients could not negotiate that restriction.Add a no-ref-delta capability and teach send-pack and pack-objects to honor it. Keep the new restriction independent of ofs-delta so servers can state exactly which object formats they accept.FromTaylor BlauDate26 Jun 2026Commita53c3b619337Patches10Git could not combine geometric repacking and cruft packs in the same operation.Roll older packs together while writing unreachable objects to a separate cruft pack. Leave packs outside the geometric rollup available and use a consistent reference snapshot when generating bitmaps.FromTaylor BlauDate12 Jun 2026Commit6afc679fa623Patches3Incremental multi-pack-index writes ignored the requested base and omitted packs needed by later layers.Honor the selected base and include newer packs so the resulting index and bitmap remain usable.

§3 Mixed · 54%

Packs above the requested base are included instead of being silently excluded from the new layer.In progresscooking here23 threadsIn our topic branches; not yet merged upstream.FromTed NymanDate28 Jul 2026Commitedb762a50b66Patches1Checking out or restoring an unchanged path rewrote the index even when nothing changed.Skip the index write when checkout does not change any entries.