From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, joey@kitenet.net
Subject: Re: What's cooking in git.git (May 2011, #06; Fri, 13)
Date: Sat, 14 May 2011 10:03:30 +0700 [thread overview]
Message-ID: <BANLkTimHdZ_9PUg509Yb7g2Oyp3qk0cKdA@mail.gmail.com> (raw)
In-Reply-To: <7vd3jm74gv.fsf@alter.siamese.dyndns.org>
On Sat, May 14, 2011 at 3:03 AM, Junio C Hamano <gitster@pobox.com> wrote:
> * jc/streaming (2011-05-12) 5 commits
> - write_entry(): use streaming API for writing working tree files
> - stream: a streaming interface to read from the object store
> - sha1_object_info_extended(): expose a bit more information from object-info
> - write_entry(): separate two helper functions out
> - packed_object_info_detail(): do not return a string
> (this branch uses jc/convert.)
>
> The counterpart to jc/bigfile to cover the write-out codepath. This does
> not yet have "read directly from pack or loose object without slurping the
> whole thing in memory" yet, which is still work in progress.
You haven't sent this to git@vger, or it failed to deliver to me.
Anyway, do you plan to extend sha1_object_info_extended() further, to
support external storage too (git-annex way for example)?
--
Duy
next prev parent reply other threads:[~2011-05-14 3:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 20:03 What's cooking in git.git (May 2011, #06; Fri, 13) Junio C Hamano
2011-05-14 3:03 ` Nguyen Thai Ngoc Duy [this message]
2011-05-14 17:37 ` Junio C Hamano
2011-05-15 4:51 ` Nguyen Thai Ngoc Duy
2011-05-15 16:50 ` Jens Lehmann
2011-05-15 20:23 ` Junio C Hamano
2011-05-17 19:43 ` [WIP PATCH] Teach read-tree the -n|--dry-run option Jens Lehmann
2011-05-17 21:15 ` Jens Lehmann
2011-05-17 22:47 ` Junio C Hamano
2011-05-19 17:47 ` [RFC PATCH] unpack-trees: add check_worktree flag to enable dry-run functionality Jens Lehmann
2011-05-19 18:14 ` Junio C Hamano
2011-05-19 18:21 ` Jens Lehmann
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=BANLkTimHdZ_9PUg509Yb7g2Oyp3qk0cKdA@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=joey@kitenet.net \
/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).