From: Jonathan Tan <jonathantanmy@google.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2017, #03; Wed, 8)
Date: Wed, 8 Mar 2017 16:46:08 -0800 [thread overview]
Message-ID: <c8f3c838-136c-2ace-509d-8600dc743ade@google.com> (raw)
In-Reply-To: <xmqqvarjz5yv.fsf@gitster.mtv.corp.google.com>
On 03/08/2017 03:47 PM, Junio C Hamano wrote:
> * jt/mark-tree-uninteresting-for-uninteresting-commit (2017-02-28) 3 commits
> - upload-pack: compute blob reachability correctly
> - revision: exclude trees/blobs given commit
> - revision: unify {tree,blob}_objects in rev_info
>
> The revision/object traversal machinery did not mark all tree and
> blob objects that are contained in an uninteresting commit as
> uninteresting, because that is quite costly. Instead, it only
> marked those that are contained in an uninteresting boundary commit
> as uninteresting.
>
> cf. <20170228215937.yd4juycjf7y3vish@sigill.intra.peff.net>
This is superseded by [1] which I just sent out. I currently have no
idea how to fix the "revision" commits to be correct and still
performant (and this might not be possible), so I wrote [1] which just
contains a partial "upload-pack" fix.
[1] <20170309003547.6930-1-jonathantanmy@google.com>
next prev parent reply other threads:[~2017-03-09 1:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 23:47 What's cooking in git.git (Mar 2017, #03; Wed, 8) Junio C Hamano
2017-03-09 0:46 ` Jonathan Tan [this message]
2017-03-09 1:01 ` brian m. carlson
2017-03-10 19:53 ` Junio C Hamano
2017-03-09 22:00 ` Johannes Schindelin
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=c8f3c838-136c-2ace-509d-8600dc743ade@google.com \
--to=jonathantanmy@google.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).