From: Derrick Stolee <derrickstolee@github.com>
To: "Junio C Hamano" <gitster@pobox.com>,
git@vger.kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Elijah Newren" <newren@gmail.com>,
"Phillip Wood" <phillip.wood123@gmail.com>,
"Taylor Blau" <ttaylorr@github.com>
Subject: ds/* (was Re: What's cooking in git.git (Jul 2022, #06; Tue, 19))
Date: Wed, 20 Jul 2022 09:22:13 -0400 [thread overview]
Message-ID: <e3b6e656-c20c-8eeb-a302-3274c8ab1f77@github.com> (raw)
In-Reply-To: <xmqqpmi04m1f.fsf@gitster.g>
On 7/19/2022 9:20 PM, Junio C Hamano wrote:
> * 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.
> * 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
next prev parent reply other threads:[~2022-07-20 13:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 1:20 What's cooking in git.git (Jul 2022, #06; Tue, 19) Junio C Hamano
2022-07-20 13:22 ` Derrick Stolee [this message]
2022-07-21 21:25 ` rs/mergesort (was: What's cooking in git.git (Jul 2022, #06; Tue, 19)) René Scharfe
2022-07-22 7:19 ` Martin Ågren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e3b6e656-c20c-8eeb-a302-3274c8ab1f77@github.com \
--to=derrickstolee@github.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.com \
--cc=phillip.wood123@gmail.com \
--cc=ttaylorr@github.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).