git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff Hostetler <git@jeffhostetler.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2017, #08; Tue, 28)
Date: Fri, 1 Dec 2017 11:49:03 -0500	[thread overview]
Message-ID: <787549da-b6ea-2c26-037c-bd4d86d316ad@jeffhostetler.com> (raw)
In-Reply-To: <xmqq1skh6fyz.fsf@gitster.mtv.corp.google.com>



On 11/28/2017 8:17 PM, Junio C Hamano wrote:
> [Cooking]
> 
> 
> * jh/object-filtering (2017-11-22) 6 commits
>    (merged to 'next' on 2017-11-27 at e5008c3b28)
>   + pack-objects: add list-objects filtering
>   + rev-list: add list-objects filtering support
>   + list-objects: filter objects in traverse_commit_list
>   + oidset: add iterator methods to oidset
>   + oidmap: add oidmap iterator methods
>   + dir: allow exclusions from blob in addition to file
>   (this branch is used by jh/fsck-promisors and jh/partial-clone.)
> 
>   In preparation for implementing narrow/partial clone, the object
>   walking machinery has been taught a way to tell it to "filter" some
>   objects from enumeration.
> 
>   Will merge to 'master'.

Could we wait on this.  I'd like to send up a V6 that
addresses the assert() questions raised.  And Jonathan
Nieder had a few suggestions that I want to address.

Thanks.
Jeff


  parent reply	other threads:[~2017-12-01 16:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29  1:17 What's cooking in git.git (Nov 2017, #08; Tue, 28) Junio C Hamano
2017-12-01 13:33 ` Johannes Schindelin
2017-12-01 13:38 ` cc/require-tcl-tk-for-build, was " Johannes Schindelin
2017-12-01 13:49 ` jt/diff-anchored-patience, " Johannes Schindelin
2017-12-01 13:56 ` Lars Schneider
2017-12-01 14:32 ` jn/reproducible-build, was " Johannes Schindelin
2017-12-01 15:41   ` Lars Schneider
2017-12-01 16:49 ` Jeff Hostetler [this message]
2017-12-03  0:27   ` 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=787549da-b6ea-2c26-037c-bd4d86d316ad@jeffhostetler.com \
    --to=git@jeffhostetler.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).