git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2023, #03; Tue, 11)
Date: Wed, 12 Apr 2023 18:04:55 -0400	[thread overview]
Message-ID: <ZDcrB0nX4Rl4ABCU@nand.local> (raw)
In-Reply-To: <xmqqo7ns69sz.fsf@gitster.g>

On Wed, Apr 12, 2023 at 02:59:56PM -0700, Junio C Hamano wrote:
> * tb/pack-bitmap-index-seek (2023-03-20) 6 commits
>  - pack-bitmap.c: factor out `bitmap_index_seek_commit()`
>  - pack-bitmap.c: use `bitmap_index_seek()` where possible
>  - pack-bitmap.c: factor out manual `map_pos` manipulation
>  - pack-bitmap.c: drop unnecessary 'inline's
>  - pack-bitmap.c: hide bitmap internals in `read_be32()`
>  - pack-bitmap.c: hide bitmap internals in `read_u8()`
>
>  Clean-up the pack-bitmap codepath.
>
>  Kicked back to 'seen' out of 'next'.
>  There is a BUG() on data errors that needs to be fixed.
>  source: <cover.1679342296.git.me@ttaylorr.com>

Sorry for letting this linger for a bit, I've been stymied with other
topics that has limited my attention on this series.

AFAICT, it shouldn't be conflicting with any other in-flight topics
right now, so keeping it in 'seen' as-is shouldn't be an issue. But if
you want to kick it out of there, too, that's equally fine with me.

I do intend on getting back to it shortly, though, hopefully next week.

Thanks,
Taylor

  reply	other threads:[~2023-04-12 22:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 21:59 What's cooking in git.git (Apr 2023, #03; Tue, 11) Junio C Hamano
2023-04-12 22:04 ` Taylor Blau [this message]
2023-04-13  0:24 ` Andrei Rybak
2023-04-13 15:06   ` Junio C Hamano
2023-04-13 22:19 ` Victoria Dye
2023-04-14  1:13   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZDcrB0nX4Rl4ABCU@nand.local \
    --to=me@ttaylorr.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.
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).