git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2012, #03; Mon, 5)
Date: Tue, 6 Mar 2012 16:40:11 +0700	[thread overview]
Message-ID: <CACsJy8BRQ63hV5e63yoMVykOMZS3u-VrdCQtvgRGBji4Yzpi4A@mail.gmail.com> (raw)
In-Reply-To: <7vmx7uurnj.fsf@alter.siamese.dyndns.org>

On Tue, Mar 6, 2012 at 2:15 PM, Junio C Hamano <gitster@pobox.com> wrote:
> * nd/stream-more (2012-03-05) 6 commits
>  - fsck: use streaming API for writing lost-found blobs
>  - show: use streaming API for showing blobs
>  - parse_object: avoid putting whole blob in core
>  - cat-file: use streaming API to print blobs
>  - Add more large blob test cases
>  - streaming: make streaming-write-entry to be more reusable
>
> As I do not think changes in the original larger series that touch
> index-pack and unpack-objects will be ready for the upcoming 1.7.10,
> I've picked up only bits that deal with "use streaming API instead
> of reading things in core" and minimally fixed them up.  These we
> should be able to polish in time.

11/11 should be safe to go too. It simply reads config files so that
parse_object() respects core.bigfilethreshold.

http://mid.gmane.org/1330919028-6611-12-git-send-email-pclouds@gmail.com

> The "test cases" patch needs to be trimmed to cover only these, I
> would think.

I'd rather leave it as is. All new test cases are test_expect_failure,
they should not interrupt "make test". If I slack off, somebody may be
annoyed enough with those known breakages to give me a little push.
-- 
Duy

  reply	other threads:[~2012-03-06  9:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06  7:15 What's cooking in git.git (Mar 2012, #03; Mon, 5) Junio C Hamano
2012-03-06  9:40 ` Nguyen Thai Ngoc Duy [this message]
2012-03-06 18:23   ` Junio C Hamano
2012-03-07 10:54     ` [PATCH 0/7] nd/stream-more updates Nguyễn Thái Ngọc Duy
2012-03-07 10:54       ` [PATCH 1/7] streaming: make streaming-write-entry to be more reusable Nguyễn Thái Ngọc Duy
2012-03-07 10:54       ` [PATCH 2/7] Add more large blob test cases Nguyễn Thái Ngọc Duy
2012-03-07 10:54       ` [PATCH 3/7] cat-file: use streaming API to print blobs Nguyễn Thái Ngọc Duy
2012-03-07 10:54       ` [PATCH 4/7] parse_object: avoid putting whole blob in core Nguyễn Thái Ngọc Duy
2012-03-07 10:54       ` [PATCH 5/7] show: use streaming API for showing blobs Nguyễn Thái Ngọc Duy
2012-03-07 10:54       ` [PATCH 6/7] fsck: use streaming API for writing lost-found blobs Nguyễn Thái Ngọc Duy
2012-03-07 10:54       ` [PATCH 7/7] update-server-info: respect core.bigfilethreshold Nguyễn Thái Ngọc Duy
2012-03-07 17:13       ` [PATCH 0/7] nd/stream-more updates Junio C Hamano
2012-03-07  6:28 ` In preparation for 1.7.10-rc0 Junio C Hamano

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=CACsJy8BRQ63hV5e63yoMVykOMZS3u-VrdCQtvgRGBji4Yzpi4A@mail.gmail.com \
    --to=pclouds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).