From: Stepan Kasal <kasal@ucw.cz>
To: git@vger.kernel.org
Subject: Eliminate curl binary
Date: Tue, 3 Jun 2008 12:53:23 +0200 [thread overview]
Message-ID: <20080603105323.GA15825@camelia.ucw.cz> (raw)
Hello,
git source code uses curl (the binary) on exactly one spot:
git-clone.sh
I would welcome if that spot were rewritten so that git would no
longer require curl, only libcurl.
(I clashed with a design flaw of curl cmd-line interfaace, so I'd
like to uninstalle it. ;-) Nothing against libcurl.)
I apologize that I'm not providing a patch, and hope that this quick
bug report (enhancement request) is better than doing nothing.
OTOH, I might write a patch later, so quick hints are welcome.
(A git-* binary shall be called insted of curl in git-clone.sh; shall
it be written from scratch, or is there a git-*.c source which can be
bended for this purpose?)
Have a nice day,
Stepan Kasal
next reply other threads:[~2008-06-03 11:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 10:53 Stepan Kasal [this message]
2008-06-03 11:14 ` Eliminate curl binary Johan Herland
2008-06-03 12:13 ` Stepan Kasal
2008-06-03 13:58 ` Stepan Kasal
2008-06-03 14:23 ` Jakub Narebski
2008-06-03 15:20 ` spec file in tarball (was: Eliminate curl binary) Stepan Kasal
2008-06-03 16:08 ` Jakub Narebski
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=20080603105323.GA15825@camelia.ucw.cz \
--to=kasal@ucw.cz \
--cc=git@vger.kernel.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).