git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (Nov 2009, #04; Tue, 17)

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Nov 18, 2009, 16:12 UTC
Message-ID
<4B041D09.8090009@viscovery.net>
In-Reply-To
<fcaeb9bf0911180643w5e659340jd845aa202e6feca3@mail.gmail.com>
Nguyen Thai Ngoc Duy schrieb:
Show 11 quoted lines
> 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
Previous: Nguyen Thai Ngoc Duy
Message 9 of 9 in “What's cooking in git.git (Nov 2009, #04; Tue, 17)”
  1. Junio C HamanoNov 18, 2009
  2. Tay Ray ChuanNov 18, 2009
  3. Johannes SixtNov 18, 2009
  4. Junio C HamanoNov 19, 2009
  5. th/remote-usageJonathan Nieder, Nov 18, 2009
  6. Jonathan NiederNov 18, 2009
  7. Tim HeniganNov 18, 2009
  8. Nguyen Thai Ngoc DuyNov 18, 2009
  9. Johannes SixtNov 18, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.