From: Michael Haggerty <mhagger@alum.mit.edu>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2012, #10; Fri, 31)
Date: Sat, 01 Sep 2012 09:28:10 +0200 [thread overview]
Message-ID: <5041B90A.5020903@alum.mit.edu> (raw)
In-Reply-To: <7v4nnin3xm.fsf@alter.siamese.dyndns.org>
On 08/31/2012 11:32 PM, Junio C Hamano wrote:
> [...]
> * mh/fetch-filter-refs (2012-08-26) 17 commits
> - filter_refs(): simplify logic
> - fetch_pack(): free matching heads
> - cmd_fetch_pack(): simplify computation of return value
> - fetch-pack: report missing refs even if no existing refs were received
> - cmd_fetch_pack: return early if finish_connect() returns an error
> - filter_refs(): compress unmatched refs in heads array
> - filter_refs(): do not leave gaps in return_refs
> - filter_refs(): simplify by removing optimization
> - Pass nr_heads to filter_refs() by reference
> - Pass nr_heads to everything_local() by reference
> - Pass nr_heads to do_pack_ref() by reference
> - Let fetch_pack() inform caller about number of unique heads
> - filter_refs(): do not check the same head_pos twice
> - fetch-pack.c: name local variables more consistently
> - fetch_pack(): reindent function decl and defn
> - Rename static function fetch_pack() to http_fetch_pack()
> - t5500: add tests of error output for missing refs
>
> Code simplification and clarification.
> Waiting for a follow-up patch based on Peff's idea.
Please hold off on merging this anywhere for now. I realized that
<nr_heads,heads> is basically a string_list, and I'm going to try
re-implementing on that basis.
Michael
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
prev parent reply other threads:[~2012-09-01 7:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-31 21:32 What's cooking in git.git (Aug 2012, #10; Fri, 31) Junio C Hamano
2012-09-01 7:28 ` Michael Haggerty [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=5041B90A.5020903@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--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 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).