git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Barkalow <barkalow@iabervon.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] Make fetch-pack a builtin with an internal API
Date: Mon, 9 Jul 2007 02:37:34 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0707090142130.6977@iabervon.org> (raw)
In-Reply-To: <7vwsxaw2xu.fsf@assigned-by-dhcp.cox.net>

On Sun, 8 Jul 2007, Junio C Hamano wrote:

> Are _identifiers with leading underscore Kosher thing to do, I
> wonder...  We do have ones with trailing ones (mostly qsort
> functions) and I think they are done that way for the sake of
> standards conformance.

I'm not sure; I inherited that bit of code from Julian. Do we have a 
standard idiom for a function that sets a bunch of static variables?

> diff --git a/fetch-pack.h b/fetch-pack.h
> new file mode 100644
> index 0000000..2bd05a8
> --- /dev/null
> +++ b/fetch-pack.h
> @@ -0,0 +1,16 @@
> +#ifndef FETCH_PACK_API
> 
> We seem to say "#ifndef FETCH_PACK_H" in such a case, though.

I was trying to convey that this is the C API to call fetch-pack directly, 
rather than something used by the builtin, or by the wrapper for calling 
the builtin. But the inclusion guard is probably not going to be noticed 
anyway, and I don't think it's worth making the header filename verbose.

> Nobody seems to call setup_fetch_pack() yet.  How complete is
> this patch meant to be?

It's part of a series that leads up to making fetch a builtin. I'm trying 
to get in bits that are bounded by logical APIs. The roadmap here is that 
transport.{c,h} from one of my other patches will get a function to fetch 
a set of refs, and it will (for a suitable URL format) call 
setup_fetch_pack() with the appropriate options and then call 
fetch_pack(). builtin-fetch will use this function to actually get objects 
once it has determined which ones it should get.

I think I've now got the whole series to a point where everything's 
submittable, if you'd like to see the whole thing. It's actually composed 
of 6 initial independant sub-series (mostly single patches) of which I've 
submitted 4 (three today and the one that modularizes the commit-walker 
infrastructure and removes the obsolete ones), and a final series of 3 
that implements fetch on top of the rest. How should I number this?

	-Daniel
*This .sig left intentionally blank*

  reply	other threads:[~2007-07-09  6:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-09  5:10 [PATCH v2] Make fetch-pack a builtin with an internal API Daniel Barkalow
2007-07-09  5:39 ` Junio C Hamano
2007-07-09  6:37   ` Daniel Barkalow [this message]
2007-07-09 18:04     ` René Scharfe
2007-07-09 18:16       ` Daniel Barkalow
2007-07-09 11:50   ` Theodore Tso
2007-07-09 13:16     ` Andy Parkins
2007-07-09 14:40       ` Theodore Tso
2007-07-09 15:10         ` Florian Weimer
2007-07-09 15:28         ` Andy Parkins

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=Pine.LNX.4.64.0707090142130.6977@iabervon.org \
    --to=barkalow@iabervon.org \
    --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).