git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Lawrence Siebert <lawrencesiebert@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] rev-list: disable --use-bitmap-index when pruning commits
Date: Wed, 01 Jul 2015 12:00:13 -0700	[thread overview]
Message-ID: <xmqq3817aeki.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20150701184217.GA8079@peff.net> (Jeff King's message of "Wed, 1 Jul 2015 14:42:17 -0400")

Jeff King <peff@peff.net> writes:

> On Wed, Jul 01, 2015 at 08:19:40AM -0700, Junio C Hamano wrote:
>
>> Sounds good.  While at it, perhaps add a mention (perhaps by
>> creating a BUGS section at the end of the file) that --count
>> with --use-bitmap-index ignores pathspec silently?
>
> I think we can just fix it rather than documenting the problem. :)

;-)  Good.

Will queue; thanks.

>
> -- >8 --
> Subject: rev-list: disable --use-bitmap-index when pruning commits
>
> The reachability bitmaps do not have enough information to
> tell us which commits might have changed path "foo", so the
> current code produces wrong answers for:
>
>   git rev-list --use-bitmap-index --count HEAD -- foo
>
> (it silently ignores the "foo" limiter). Instead, we should
> fall back to doing a normal traversal (it is OK to fall
> back rather than complain, because --use-bitmap-index is a
> pure optimization, and might not kick in for other reasons,
> such as there being no bitmaps in the repository).
>
> Signed-off-by: Jeff King <peff@peff.net>
> ---
>  builtin/rev-list.c      | 2 +-
>  t/t5310-pack-bitmaps.sh | 6 ++++++
>  2 files changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/builtin/rev-list.c b/builtin/rev-list.c
> index ff84a82..88eddbd 100644
> --- a/builtin/rev-list.c
> +++ b/builtin/rev-list.c
> @@ -355,7 +355,7 @@ int cmd_rev_list(int argc, const char **argv, const char *prefix)
>  	if (bisect_list)
>  		revs.limited = 1;
>  
> -	if (use_bitmap_index) {
> +	if (use_bitmap_index && !revs.prune) {
>  		if (revs.count && !revs.left_right && !revs.cherry_mark) {
>  			uint32_t commit_count;
>  			if (!prepare_bitmap_walk(&revs)) {
> diff --git a/t/t5310-pack-bitmaps.sh b/t/t5310-pack-bitmaps.sh
> index 6003490..d446706 100755
> --- a/t/t5310-pack-bitmaps.sh
> +++ b/t/t5310-pack-bitmaps.sh
> @@ -53,6 +53,12 @@ rev_list_tests() {
>  		test_cmp expect actual
>  	'
>  
> +	test_expect_success "counting commits with limiting ($state)" '
> +		git rev-list --count HEAD -- 1.t >expect &&
> +		git rev-list --use-bitmap-index --count HEAD -- 1.t >actual &&
> +		test_cmp expect actual
> +	'
> +
>  	test_expect_success "enumerate --objects ($state)" '
>  		git rev-list --objects --use-bitmap-index HEAD >tmp &&
>  		cut -d" " -f1 <tmp >tmp2 &&

      reply	other threads:[~2015-07-01 19:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-01  9:24 [PATCH] rev-list: add --count to usage guide Lawrence Siebert
2015-07-01 15:19 ` Junio C Hamano
2015-07-01 18:42   ` [PATCH] rev-list: disable --use-bitmap-index when pruning commits Jeff King
2015-07-01 19:00     ` Junio C Hamano [this message]

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=xmqq3817aeki.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=lawrencesiebert@gmail.com \
    --cc=peff@peff.net \
    /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).