From: "Shawn O. Pearce" <spearce@spearce.org>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] Push code for transport library
Date: Sun, 8 Jul 2007 17:14:18 -0400 [thread overview]
Message-ID: <20070708211418.GA4436@spearce.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0707081608100.6977@iabervon.org>
Daniel Barkalow <barkalow@iabervon.org> wrote:
> This moves the code to call push backends into a library that can be
> extended to make matching fetch and push decisions based on the URL it
> gets, and which could be changed to have built-in implementations
> instead of calling external programs.
...
> +static const struct transport_ops git_transport = {
> + .set_option = set_git_option,
> + .push = git_transport_push
> +};
Interesting.
But can we please avoid that struct initialization syntax?
I build Git with a C compiler that doesn't understand it. No, I
can't upgrade the compiler. In the past we've largely been able
to avoid using this feature of C99. If you look at the current
codebase this would again become the first usage of the feature,
as I have long since eliminated all of them.
--
Shawn.
prev parent reply other threads:[~2007-07-08 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 20:09 [PATCH] Push code for transport library Daniel Barkalow
2007-07-08 20:29 ` Johannes Schindelin
2007-07-08 21:14 ` Shawn O. Pearce [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=20070708211418.GA4436@spearce.org \
--to=spearce@spearce.org \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).