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

ds/* (was Re: What's cooking in git.git (Jul 2022, #06; Tue, 19))

From
Derrick Stolee <derrickstolee@github.com>
Date
Jul 20, 2022, 13:22 UTC
Message-ID
<e3b6e656-c20c-8eeb-a302-3274c8ab1f77@github.com>
In-Reply-To
<xmqqpmi04m1f.fsf@gitster.g>
On 7/19/2022 9:20 PM, Junio C Hamano wrote:
Show 11 quoted lines
> * ds/midx-with-less-memory (2022-07-19) 3 commits
>  - midx: reduce memory pressure while writing bitmaps
>  - midx: extract bitmap write setup
>  - pack-bitmap-write: use const for hashes
> 
>  The codepath to write multi-pack index has been taught to release a
>  large chunk of memory that holds an array of objects in the packs,
>  as soon as it is done with the array, to reduce memory consumption.
> 
>  Will merge to 'next'?
>  source: <pull.1292.v2.git.1658244366.gitgitgadget@gmail.com>

The actual functional change is very small and safe. I don't expect significant edits to follow the latest version, but I'm happy to wait a few more days if someone wants to chime in.

Show 20 quoted lines
> * ds/rebase-update-ref (2022-07-19) 13 commits
>  - sequencer: notify user of --update-refs activity
>  - sequencer: ignore HEAD ref under --update-refs
>  - rebase: add rebase.updateRefs config option
>  - sequencer: rewrite update-refs as user edits todo list
>  - rebase: update refs from 'update-ref' commands
>  - rebase: add --update-refs option
>  - sequencer: add update-ref command
>  - sequencer: define array with enum values
>  - rebase-interactive: update 'merge' description
>  - branch: consider refs under 'update-refs'
>  - t2407: test branches currently using apply backend
>  - t2407: test bisect and rebase as black-boxes
>  - Merge branch 'ds/branch-checked-out' into ds/rebase-update-ref
> 
>  "git rebase -i" learns to update branches whose tip appear in the
>  rebased range.
> 
>  Will merge to 'next'?
>  source: <pull.1247.v5.git.1658255624.gitgitgadget@gmail.com>

The most recent version was finally an iteration of small fixes, and not a rework of anything substantial. There are several things being saved for a possible follow-up, but I'm eager to see more people give this a try. I'll watch closely for any need to forward- fix anything in this area.

Thanks, -Stolee

Previous: Junio C HamanoNext: René Scharfe
Message 2 of 4 in “What's cooking in git.git (Jul 2022, #06; Tue, 19)”
  1. Junio C HamanoJul 20, 2022
  2. ds/* (was Re: What's cooking in git.git (Jul 2022, #06; Tue, 19))Derrick Stolee, Jul 20, 2022
  3. rs/mergesort (was: What's cooking in git.git (Jul 2022, #06; Tue, 19))René Scharfe, Jul 21, 2022
  4. Martin ÅgrenJul 22, 2022

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.