From: Johannes Sixt <j.sixt@viscovery.net>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2009, #04; Tue, 17)
Date: Wed, 18 Nov 2009 17:12:57 +0100 [thread overview]
Message-ID: <4B041D09.8090009@viscovery.net> (raw)
In-Reply-To: <fcaeb9bf0911180643w5e659340jd845aa202e6feca3@mail.gmail.com>
Nguyen Thai Ngoc Duy schrieb:
> On 11/18/09, Junio C Hamano <gitster@pobox.com> wrote:
>> * nd/sparse (2009-08-20) 19 commits.
>>
>> The latest update I didn't look at very closely but I had an impression
>> that it was touching very generic codepath that would affect non sparse
>> cases, iow the patch looked very scary (the entire series already is).
>
> I wonder if there is any other approach for sparse checkout? I'll see
> if I can improve it, but with a series touching unpack logic, diff
> core, .gitattributes/.gitignore, it's hard to get it right and
> obvious.
Just FYI: I run some of my installations with this series, but without
using sparse checkout to see if there are regressions. Nothing came up so
far.
-- Hannes
prev parent reply other threads:[~2009-11-18 16:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 7:53 What's cooking in git.git (Nov 2009, #04; Tue, 17) Junio C Hamano
2009-11-18 8:22 ` Tay Ray Chuan
2009-11-18 8:40 ` Johannes Sixt
2009-11-19 18:11 ` Junio C Hamano
2009-11-18 11:48 ` th/remote-usage Jonathan Nieder
2009-11-18 12:05 ` th/remote-usage Jonathan Nieder
2009-11-18 21:28 ` th/remote-usage Tim Henigan
2009-11-18 14:43 ` What's cooking in git.git (Nov 2009, #04; Tue, 17) Nguyen Thai Ngoc Duy
2009-11-18 16:12 ` Johannes Sixt [this message]
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=4B041D09.8090009@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.