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

Re: What's cooking in git.git (Nov 2009, #03; Sun, 15)

From
PWPeter Weseloh <peter.weseloh@gmail.com>
Date
Nov 15, 2009, 23:40 UTC
Message-ID
<loom.20091116T003914-635@post.gmane.org>
In-Reply-To
<7vtywwm6i4.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster <at> pobox.com> writes:
Show 5 quoted lines
> * 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).

Hi, I'm new here so first of all thanks a lot for such a great tool!

Does that mean this feature will not make it into 'master' any time soon? I'm currently trying to convince my managment to switch from CVS to git. What causes some trouble is that we have quite some files (> 40k) in various (>300) CVS modules and splitting them into sub-repos seams somewhat difficult. git has no problem even with that many files but commands that stat the working copy (e.g. 'git status') take quite long on our filers (it's either a problem with the filers or with nfs or both, I don't know yet). Having the ability to do sparse checkouts only of the repo sounds like a way out.

Annother question: What's the timeline for 1.7.0? I couldn't find anything about it neither here nor in the wiki.

Thanks, Peter

Previous: Junio C HamanoNext: James Pickens
Message 6 of 8 in “What's cooking in git.git (Nov 2009, #03; Sun, 15)”
  1. Junio C HamanoNov 15, 2009
  2. Daniel BarkalowNov 15, 2009
  3. Sverre RabbelierNov 15, 2009
  4. Daniel BarkalowNov 16, 2009
  5. Junio C HamanoNov 16, 2009
  6. Peter WeselohNov 15, 2009
  7. James PickensNov 16, 2009
  8. Junio C HamanoNov 16, 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.