Re: sparse fetch, was Re: [PATCH 08/12] git-clone: support --path to do sparse clone

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Thu, 24 Jul 2008, Jeff King wrote:

> On Thu, Jul 24, 2008 at 06:41:03PM +0100, Johannes Schindelin wrote:
> 
> > > As a user, I would expect "sparse clone" to also be sparse on the 
> > > fetching. That is, to not even bother fetching tree objects that we 
> > > are not going to check out. But that is a whole other can of worms 
> > > from local sparseness, so I think it is worth saving for a different 
> > > series.
> > 
> > I think this is not even worth of a series.  Sure, it would have 
> > benefits for those who want sparse checkouts.  But it comes for a high 
> > price on everyone else:
> 
> I agree there are a lot of issues. I am just thinking of the person who 
> said they had a >100G repository. But I am also not volunteering to do 
> it, so I will let somebody who really cares about it try to defend the 
> idea.

I never said that there were no benefits.  I argued that there are too 
many _downsides_ to those who _don't_ benefit.

Ciao,
Dscho

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux