From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: git-pull from git.git - no remote ref for pu or next?
Date: Tue, 12 Dec 2006 20:15:41 +0100 [thread overview]
Message-ID: <elmv0c$kmd$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.63.0612121956470.2807@wbgn013.biozentrum.uni-wuerzburg.de
Johannes Schindelin wrote:
> But it would become a non-problem when the HTTP transport would learn to
> read and interpret the .idx files, basically constructing thin packs from
> parts of the .pack files ("Content-Range:" comes to mind)...
cURL the CLI can do this with -r/--range option, so I think that curl
the library can do this too. Mind you, this is HTTP/1.1 extension
(hmmm... I wonder if many sites run HTTP/1.0 only).
See also: http://www.linux.com/article.pl?sid=06/10/10/1824245
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-12-12 19:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 16:44 git-pull from git.git - no remote ref for pu or next? Randal L. Schwartz
2006-12-12 16:47 ` Randal L. Schwartz
2006-12-12 17:40 ` Johannes Schindelin
2006-12-12 17:42 ` Randal L. Schwartz
2006-12-12 17:56 ` Linus Torvalds
2006-12-12 18:09 ` Johannes Schindelin
2006-12-12 18:23 ` Linus Torvalds
2006-12-12 19:07 ` Nicolas Pitre
2006-12-12 19:13 ` Linus Torvalds
2006-12-12 19:18 ` Jakub Narebski
2006-12-12 18:54 ` Nicolas Pitre
2006-12-12 19:04 ` Johannes Schindelin
2006-12-12 19:15 ` Jakub Narebski [this message]
2006-12-12 19:26 ` Nicolas Pitre
2006-12-12 19:32 ` Johannes Schindelin
2006-12-12 19:48 ` Linus Torvalds
2006-12-12 20:04 ` Jakub Narebski
2006-12-12 20:26 ` Johannes Schindelin
2006-12-12 19:50 ` Nicolas Pitre
2006-12-12 18:51 ` Nicolas Pitre
2006-12-12 19:03 ` Linus Torvalds
2006-12-12 21:26 ` Eric Wong
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='elmv0c$kmd$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--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).