From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Tay Ray Chuan <rctay89@gmail.com>
Cc: Sverre Rabbelier <srabbelier@gmail.com>,
Gabriel Filion <lelutin@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Michael J Gruber <git@drmicha.warpmail.net>,
Jonathan Nieder <jrnieder@gmail.com>,
Daniel Barkalow <barkalow@iabervon.org>,
Git Mailing List <git@vger.kernel.org>,
Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
Subject: Re: [PATCH v7 1/2] Documentation/remote-helpers: Rewrite description
Date: Mon, 29 Mar 2010 09:15:43 +0530 [thread overview]
Message-ID: <f3271551003282045q1aea17dbm336ce2db8a11453f@mail.gmail.com> (raw)
In-Reply-To: <be6fef0d1003282025p4a472b79hb02959fea7481065@mail.gmail.com>
Hi,
> I think "family" is confusing. They're all symlinks of
> git-remote-curl, if I remember correctly.
Actually, there's no Makefile target called git-remote-curl. See
Makefile:1122 to Makefile:1126. They're copies in my build.
REMOTE_CURL_PRIMARY = git-remote-http$X
REMOTE_CURL_ALIASES = git-remote-https$X git-remote-ftp$X git-remote-ftps$X
REMOTE_CURL_NAMES = $(REMOTE_CURL_PRIMARY) $(REMOTE_CURL_ALIASES)
PROGRAM_OBJS += http-fetch.o
PROGRAMS += $(REMOTE_CURL_NAMES)
> But then, I suspect you'll be rewriting this portion, since Ilari's
> notes has a thing or two why helper names have the protocol in them.
Right. Thanks for pointing this out.
-- Ram
next prev parent reply other threads:[~2010-03-29 3:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-28 18:03 [PATCH v7 1/2] Documentation/remote-helpers: Rewrite description Ramkumar Ramachandra
2010-03-29 1:17 ` Gabriel Filion
2010-03-29 3:04 ` Ramkumar Ramachandra
2010-03-29 3:08 ` Sverre Rabbelier
2010-03-29 5:09 ` Daniel Barkalow
2010-03-29 6:18 ` Ramkumar Ramachandra
2010-03-29 6:39 ` Jonathan Nieder
2010-03-29 15:39 ` Daniel Barkalow
2010-03-30 3:23 ` Ramkumar Ramachandra
2010-03-29 3:25 ` Tay Ray Chuan
2010-03-29 3:45 ` Ramkumar Ramachandra [this message]
2010-04-05 14:05 ` Ramkumar Ramachandra
2010-04-05 21:55 ` Junio C Hamano
2010-04-06 2:47 ` Ramkumar Ramachandra
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=f3271551003282045q1aea17dbm336ce2db8a11453f@mail.gmail.com \
--to=artagnon@gmail.com \
--cc=barkalow@iabervon.org \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ilari.liusvaara@elisanet.fi \
--cc=jrnieder@gmail.com \
--cc=lelutin@gmail.com \
--cc=rctay89@gmail.com \
--cc=srabbelier@gmail.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).