From: Peter Weseloh <Peter.Weseloh@gmail.com>
To: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2009, #03; Sun, 15)
Date: Sun, 15 Nov 2009 23:40:44 +0000 (UTC) [thread overview]
Message-ID: <loom.20091116T003914-635@post.gmane.org> (raw)
In-Reply-To: 7vtywwm6i4.fsf@alter.siamese.dyndns.org
Junio C Hamano <gitster <at> pobox.com> writes:
> * 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
next prev parent reply other threads:[~2009-11-15 23:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-15 10:23 What's cooking in git.git (Nov 2009, #03; Sun, 15) Junio C Hamano
2009-11-15 22:26 ` Daniel Barkalow
2009-11-15 23:32 ` Sverre Rabbelier
2009-11-16 0:30 ` Daniel Barkalow
2009-11-16 0:11 ` Junio C Hamano
2009-11-15 23:40 ` Peter Weseloh [this message]
2009-11-16 0:13 ` James Pickens
2009-11-16 0:26 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20091116T003914-635@post.gmane.org \
--to=peter.weseloh@gmail.com \
--cc=git@vger.kernel.org \
/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