From: Daniel Barkalow <barkalow@iabervon.org>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH 3/4] Build-in send-pack, with an API for other programs to call.
Date: Mon, 29 Oct 2007 21:19:51 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0710292119080.7357@iabervon.org> (raw)
In-Reply-To: <20071030011401.GU14735@spearce.org>
On Mon, 29 Oct 2007, Shawn O. Pearce wrote:
> Daniel Barkalow <barkalow@iabervon.org> wrote:
> > -int main(int argc, char **argv)
> > +void setup_send_pack(struct send_pack_args *args)
> > +{
> > + receivepack = args->receivepack;
> > + verbose = args->verbose;
> > + send_all = args->send_all;
> > + force_update = args->force_update;
> > + use_thin_pack = args->use_thin_pack;
> > + dry_run = args->dry_run;
> > +}
> ...
> > +struct send_pack_args {
> > + const char *receivepack;
> > + int verbose;
> > + int send_all;
> > + int force_update;
> > + int use_thin_pack;
> > + int dry_run;
> > +};
> > +
>
> Ick. How about doing what I did with builtin-fetch-pack.c which
> was to copy the args into a global "static struct fetch_pack_args"
> and make the struct a bitfield with these boolean items as ":1"
> rather than a full int?
Yeah, that's better. I'll respin parts 3 and 4 that way.
-Daniel
*This .sig left intentionally blank*
prev parent reply other threads:[~2007-10-30 1:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 1:05 [PATCH 3/4] Build-in send-pack, with an API for other programs to call Daniel Barkalow
2007-10-30 1:14 ` Shawn O. Pearce
2007-10-30 1:18 ` Shawn O. Pearce
2007-10-30 1:19 ` Daniel Barkalow [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=Pine.LNX.4.64.0710292119080.7357@iabervon.org \
--to=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=spearce@spearce.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;
as well as URLs for NNTP newsgroup(s).