user/sven/git.git/streaming.c, branch v1.8.0.2

pack-objects, streaming: turn "xx >= big_file_threshold" to ".. > .."

2012-05-18T21:21:19Z

This is because all other places do "xx > big_file_threshold" Signed-off-by: Nguyễn Thái Ngọc Duy Signed-off-by: Junio C Hamano

streaming: void pointer instead of char pointer

2012-05-03T17:22:56Z

Allow any kind of buffer to be fed to read_istream() without an explicit cast by making it's buf argument a void pointer. It's about arbitrary data, not only characters. Signed-off-by: Rene Scharfe Signed-off-by: Nguyễn Thái Ngọc Duy Signed-off-by: Junio C Hamano

streaming: make streaming-write-entry to be more reusable

2012-03-07T17:07:37Z

The static function in entry.c takes a cache entry and streams its blob contents to a file in the working tree. Refactor the logic to a new API function stream_blob_to_fd() that takes an object name and an open file descriptor, so that it can be reused by other callers. Signed-off-by: Nguyễn Thái Ngọc Duy Signed-off-by: Junio C Hamano

Merge branch 'jc/streaming-filter'

2011-08-01T22:00:29Z

* jc/streaming-filter: streaming: free git_istream upon closing

streaming: free git_istream upon closing

2011-07-22T21:30:49Z

Kirill Smelkov noticed that post-1.7.6 "git checkout" started leaking tons of memory. The streaming_write_entry function properly calls close_istream(), but that function did not actually free() the allocated git_istream struct. The git_istream struct is totally opaque to calling code, and must be heap-allocated by open_istream. Therefore it's not appropriate for callers to have to free it. This patch makes close_istream() into "close and de-allocate all associated resources". We could add a new "free_istream" call, but there's not much point in letting callers inspect the istream after close. And this patch's semantics make us match fopen/fclose, which is well-known and understood. Signed-off-by: Jeff King Signed-off-by: Junio C Hamano

Merge branch 'jc/zlib-wrap'

2011-07-19T16:33:04Z

* jc/zlib-wrap: zlib: allow feeding more than 4GB in one go zlib: zlib can only process 4GB at a time zlib: wrap deflateBound() too zlib: wrap deflate side of the API zlib: wrap inflateInit2 used to accept only for gzip format zlib: wrap remaining calls to direct inflate/inflateEnd zlib wrapper: refactor error message formatter Conflicts: sha1_file.c

stream filter: add "no more input" to the filters

2011-05-26T23:47:15Z

Some filters may need to buffer the input and look-ahead inside it to decide what to output, and they may consume more than zero bytes of input and still not produce any output. After feeding all the input, pass NULL as input as keep calling stream_filter() to let such filters know there is no more input coming, and it is time for them to produce the remaining output based on the buffered input. Signed-off-by: Junio C Hamano

Add streaming filter API

2011-05-26T23:47:15Z

This introduces an API to plug custom filters to an input stream. The caller gets get_stream_filter("path") to obtain an appropriate filter for the path, and then uses it when opening an input stream via open_istream(). After that, the caller can read from the stream with read_istream(), and close it with close_istream(), just like an unfiltered stream. This only adds a "null" filter that is a pass-thru filter, but later changes can add LF-to-CRLF and other filters, and the callers of the streaming API do not have to change. Signed-off-by: Junio C Hamano

streaming: read loose objects incrementally

2011-05-21T06:16:53Z

Helped-by: Jeff King Signed-off-by: Junio C Hamano

streaming: read non-delta incrementally from a pack

2011-05-21T06:16:53Z

Helped-by: Jeff King Signed-off-by: Junio C Hamano