Re: What's cooking in git.git (Mar 2018, #03; Wed, 14)

From: Duy Nguyen <pclouds@gmail.com>
Date: Mar 15, 2018, 06:30 UTC
Message-ID: <CACsJy8D9-OaU5F+bugpgaPBPV_cdtqeYJ_5iYYMcrDj5d-9z5Q@mail.gmail.com>
In-Reply-To: <xmqqefkm6s06.fsf@gitster-ct.c.googlers.com>

On Thu, Mar 15, 2018 at 2:34 AM, Junio C Hamano <gitster@pobox.com> wrote:

Show 16 quoted lines

> * nd/pack-objects-pack-struct (2018-03-05) 9 commits
>  - pack-objects: reorder 'hash' to pack struct object_entry
>  - pack-objects: refer to delta objects by index instead of pointer
>  - pack-objects: move in_pack out of struct object_entry
>  - pack-objects: move in_pack_pos out of struct object_entry
>  - pack-objects: note about in_pack_header_size
>  - pack-objects: use bitfield for object_entry::depth
>  - pack-objects: use bitfield for object_entry::dfs_state
>  - pack-objects: turn type and in_pack_type to bitfields
>  - pack-objects: document holes in struct object_entry.h
>
>  "git pack-objects" needs to allocate tons of "struct object_entry"
>  while doing its work, and shrinking its size helps the performance
>  quite a bit.
>
>  Will merge to 'next'.

Hold it. A reroll is coming. I'm a bit busy this week and can't really do much.

Show 10 quoted lines

> * nd/worktree-prune (2018-03-06) 3 commits
>  - worktree prune: improve prune logic when worktree is moved
>  - worktree: delete dead code
>  - gc.txt: more details about what gc does
>
>  The way "git worktree prune" worked internally has been simplified,
>  by assuming how "git worktree move" moves an existing worktree to a
>  different place.
>
>  Will merge to 'next'.

Same.

-- 
Duy