From: Daniel Barkalow <barkalow@iabervon.org>
To: git@vger.kernel.org
Cc: Linus Torvalds <torvalds@osdl.org>, Petr Baudis <pasky@ucw.cz>
Subject: [PATCH 0/2] Support for packs in HTTP
Date: Sun, 10 Jul 2005 15:53:18 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0507101539220.30848-100000@iabervon.org> (raw)
This series has one patch which is ready to go in and one that's not
(although it's a reasonable phony for the current state of the git world).
1: Several additional functions are needed in the library to support
progressively getting pack data from some remote location and using it
to determine what else to get.
2: git-http-pull can get packs as appropriate by getting all the index
files first, and then using them to figure out whether the object it's
looking for is in some pack it could get.
Currently, there's no sane way to figure out what pack/index files are
available from an HTTP server. But there only seems to be one pack file
available on an HTTP server at the moment, so this tries to get that
one.
-Daniel
*This .sig left intentionally blank*
next reply other threads:[~2005-07-10 20:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-10 19:53 Daniel Barkalow [this message]
2005-07-10 19:55 ` [PATCH 1/2] Management of packs not yet installed Daniel Barkalow
2005-07-10 19:56 ` [PATCH 2/2] Demo support for packs via HTTP Daniel Barkalow
2005-07-11 21:49 ` Darrin Thompson
2005-07-12 1:54 ` Daniel Barkalow
2005-07-12 13:35 ` Darrin Thompson
2005-07-10 23:10 ` [PATCH 0/2] Support for packs in HTTP Junio C Hamano
2005-07-10 23:45 ` Linus Torvalds
2005-07-11 0:20 ` Daniel Barkalow
2005-07-11 0:34 ` Linus Torvalds
2005-07-11 3:22 ` Daniel Barkalow
2005-07-11 3:37 ` Linus Torvalds
2005-07-11 4:07 ` Daniel Barkalow
2005-07-11 17:44 ` Linus Torvalds
2005-07-11 20:03 ` Daniel Barkalow
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.21.0507101539220.30848-100000@iabervon.org \
--to=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
--cc=torvalds@osdl.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).