Re: What's cooking in git.git (Aug 2026, #12)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]




Junio C Hamano <gitster@xxxxxxxxx> writes:
> * tc/replay-linearize (2026年07月28日) 3 commits
> - replay: offer an option to linearize the commit topology
> - replay: resolve the replay base outside pick_regular_commit()
> - replay: add helper to put entry into replayed_commits
>
> The 'git replay' command has been taught the '--linearize' option to
> drop merge commits and linearize the replayed history, mimicking 'git
> rebase --no-rebase-merges'.
>
> Waiting for response for too long, stalled.
> cf. <anYLeQj4Sx2vZqvy@denethor>
> cf. <CABPp-BEFGku8msiJCcXburV+tcersr6uqEumKaPh-TguA1LjSg@xxxxxxxxxxxxxx>
> source: <20260728-toon-git-replay-drop-merges-v8-0-ced11dffe749@xxxxxxxxx>
Sorry it took me some longer because I was on leave. I've sent out v9
just now.
> * tc/last-modified-bloom (2026年08月07日) 6 commits
> - last-modified: keep per-path Bloom filters for wildcard pathspecs
> - last-modified: check pathspec against Bloom filter first
> - revision: add Bloom check that includes parent directories
> - bloom: add helper to check if any key in a vector is present
> - revision: expose check for paths maybe changed in Bloom filter
> - revision: move bloom keyvec precondition into function
>
> The 'git last-modified' command has been optimized by using Bloom
> filters. It now reuses revision walk filtering logic from 'git log'
> to pre-filter commits, and maintains per-path Bloom filters even when
> wildcard pathspecs are used.
>
> Waiting for response.
> cf. <xmqqtsp4a6c2.fsf@gitster.g>
> source: <20260807-toon-speed-up-last-modified-v2-0-7d87bbdeaf9b@xxxxxxxxx>
Rerolled v3.
-- 
Laters,
Toon

[Index of Archives] [Linux Kernel Development] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users]

(追記) (追記ここまで)
Powered by Linux

AltStyle によって変換されたページ (->オリジナル) /