diff options
| author | Shawn O. Pearce <spearce@spearce.org> | 2009-10-30 17:47:42 -0700 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2009-11-04 17:58:15 -0800 |
| commit | 249b2004d8c9c58ed1ea1665dfd376af0312ed7e (patch) | |
| tree | 0cb623c3c20fbaef90028db3f1272dbe1b9d211e /fetch-pack.h | |
| parent | de1a2fdd38b138c4e4fed6412783dcb74d63d2da (diff) | |
| download | git-249b2004d8c9c58ed1ea1665dfd376af0312ed7e.tar.gz | |
Smart fetch over HTTP: client side
The git-remote-curl backend detects if the remote server supports
the git-upload-pack service, and if so, runs git-fetch-pack locally
in a pipe to generate the want/have commands.
The advertisements from the server that were obtained during the
discovery are passed into git-fetch-pack before the POST request
starts, permitting server capability discovery and enablement.
Common objects that are discovered are appended onto the request as
have lines and are sent again on the next request. This allows the
remote side to reinitialize its in-memory list of common objects
during the next request.
Because all requests are relatively short, below git-remote-curl's
1 MiB buffer limit, requests will use the standard Content-Length
header and be valid HTTP/1.0 POST requests. This makes the fetch
client more tolerant of proxy servers which don't support HTTP/1.1
or the chunked transfer encoding.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
CC: Daniel Barkalow <barkalow@iabervon.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'fetch-pack.h')
| -rw-r--r-- | fetch-pack.h | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/fetch-pack.h b/fetch-pack.h index 8bd9c32561..fbe85ac05f 100644 --- a/fetch-pack.h +++ b/fetch-pack.h @@ -13,7 +13,8 @@ struct fetch_pack_args fetch_all:1, verbose:1, no_progress:1, - include_tag:1; + include_tag:1, + stateless_rpc:1; }; struct ref *fetch_pack(struct fetch_pack_args *args, |