From: Junio C Hamano <gitster@pobox.com>
To: Brandon Casey <drafnel@gmail.com>
Cc: git@vger.kernel.org, Nicolas Pitre <nico@cam.org>
Subject: Re: [PATCH v2 2/2] pack-objects: don't loosen objects available in alternate or kept packs
Date: Sun, 22 Mar 2009 12:06:41 -0700 [thread overview]
Message-ID: <7viqm15qda.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <7vbpru9nh9.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Sat, 21 Mar 2009 21:43:14 -0700")
Junio C Hamano <gitster@pobox.com> writes:
>> +static int has_sha1_pack_kept_or_nonlocal(const unsigned char *sha1)
>> +{
>> + static struct packed_git *last_found = (void *)1;
>> + struct packed_git *p;
>> +
>> + p = (last_found == (void *)1) ? packed_git : last_found;
>
> Why (void *)1, not like:
>
> static struct packed_git *last_found;
> struct packed_git *p = last_found ? last_found : packed_git;
>
> Am I missing something?
>
>> + while (p) {
>> + if ((!p->pack_local || p->pack_keep) &&
>> + find_pack_entry_one(sha1, p)) {
>> + last_found = p;
>> + return 1;
>> + }
>> + if (p == last_found)
>> + p = packed_git;
>> + else
>> + p = p->next;
>> + if (p == last_found)
>> + p = p->next;
>> + }
>> + return 0;
>> +}
Yes I was.
If you allow (last_found == NULL), the loop iterates over packed_git list,
and when it has its last element in p after discovering nothing matches
the criteria, this happens:
if (p == last_found) /* false, p is the last element on the list */
p = packed_git; /* not taken */
else
p = p->next; /* taken, p == NULL now */
if (p == last_found) /* true! */
p = p->next; /* OOPS */
next prev parent reply other threads:[~2009-03-22 19:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 22:26 [PATCH v2 2/2] pack-objects: don't loosen objects available in alternate or kept packs Brandon Casey
2009-03-22 4:43 ` Junio C Hamano
2009-03-22 14:48 ` Brandon Casey
2009-03-22 17:40 ` Nicolas Pitre
2009-03-22 19:06 ` Junio C Hamano [this message]
2009-03-22 19:23 ` Nicolas Pitre
2009-03-24 23:01 ` Brandon Casey
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=7viqm15qda.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=drafnel@gmail.com \
--cc=git@vger.kernel.org \
--cc=nico@cam.org \
/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