From: Duy Nguyen <pclouds@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Mar 2018, #03; Wed, 14)
Date: Thu, 15 Mar 2018 07:30:53 +0100 [thread overview]
Message-ID: <CACsJy8D9-OaU5F+bugpgaPBPV_cdtqeYJ_5iYYMcrDj5d-9z5Q@mail.gmail.com> (raw)
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:
> * 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.
> * 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
next prev parent reply other threads:[~2018-03-15 6:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 1:34 What's cooking in git.git (Mar 2018, #03; Wed, 14) Junio C Hamano
2018-03-15 6:30 ` Duy Nguyen [this message]
2018-03-15 16:54 ` Junio C Hamano
2018-03-15 8:36 ` Ævar Arnfjörð Bjarmason
2018-03-15 17:33 ` Junio C Hamano
2018-03-19 21:16 ` Derrick Stolee
2018-03-15 19:18 ` Lars Schneider
2018-03-15 23:00 ` Lars Schneider
2018-03-16 0:54 ` Junio C Hamano
2018-03-16 21:31 ` Jonathan Tan
2018-03-16 21:52 ` Junio C Hamano
2018-03-16 22:08 ` Jonathan Nieder
2018-03-17 0:53 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACsJy8D9-OaU5F+bugpgaPBPV_cdtqeYJ_5iYYMcrDj5d-9z5Q@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).