All of lore.kernel.org
 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 (Aug 2020, #02; Mon, 10)
Date: Tue, 11 Aug 2020 09:48:55 -0400	[thread overview]
Message-ID: <20200811134855.GA19871@syl.lan> (raw)
In-Reply-To: <xmqqsgcub811.fsf@gitster.c.googlers.com>

On Mon, Aug 10, 2020 at 12:44:26PM -0700, Junio C Hamano wrote:
> Here are the topics that have been cooking.  Commits prefixed with '-' are
> only in 'seen' (formerly 'pu'---proposed updates) while commits prefixed
> with '+' are in 'next'.  The ones marked with '.' do not appear in any of
> the integration branches, but I am still holding onto them.

I noticed that you picked up 'tb/bloom-improvements' in your fork, but
that it didn't make it into the list of cooking topics below. I suspect
that this is because of [1], where I got bitten by trying to sneak in an
extra 'bitmap_free()' at the last moment.

I have a fixup in [2] which needs to be squashed in at that point in the
series, along with dropping a '&' in the last patch to squelch a
compiler error introduced by the fixup.

Do you want me to resend the whole series, or would you rather apply the
fixups when queuing? Either is fine for me.

> * tb/upload-pack-filters (2020-08-05) 4 commits
>   (merged to 'next' on 2020-08-05 at 918e7092fe)
>  + t5616: use test_i18ngrep for upload-pack errors
>   (merged to 'next' on 2020-08-04 at 3ae57cc90c)
>  + upload-pack.c: introduce 'uploadpackfilter.tree.maxDepth'
>  + upload-pack.c: allow banning certain object filter(s)
>  + list_objects_filter_options: introduce 'list_object_filter_config_name'
>
>  The component to respond to "git fetch" request is made more
>  configurable to selectively allow or reject object filtering
>  specification used for partial cloning.
>
>  Will merge to 'master'.
>  cf. <20200804003722.GA2726931@coredump.intra.peff.net>

Thanks, I'm glad that this made it in.

Thanks,
Taylor

[1]: https://lore.kernel.org/git/xmqqbljoolhy.fsf@gitster.c.googlers.com/
[2]: https://lore.kernel.org/git/20200811134807.GA26715@syl.lan/

  parent reply	other threads:[~2020-08-11 13:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10 19:44 What's cooking in git.git (Aug 2020, #02; Mon, 10) Junio C Hamano
2020-08-11  5:01 ` Eric Sunshine
2020-08-11 19:24   ` Junio C Hamano
2020-08-11  6:53 ` Jeff King
2020-08-11  9:33   ` Patrick Steinhardt
2020-08-11  9:59   ` brian m. carlson
2020-08-11 10:10 ` Sergey Organov
2020-08-11 19:23   ` Junio C Hamano
2020-08-11 19:34     ` Sergey Organov
2020-08-11 20:17       ` Sergey Organov
2020-08-11 21:36         ` Junio C Hamano
2020-08-12  8:15           ` Sergey Organov
2020-08-11 20:28       ` Junio C Hamano
2020-08-11 21:26         ` Sergey Organov
2020-08-11 22:12           ` Junio C Hamano
2020-08-11 13:48 ` Taylor Blau [this message]
2020-08-11 14:27 ` Matheus Tavares Bernardino
2020-08-11 19:20   ` 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=20200811134855.GA19871@syl.lan \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.