Re: How hard would it be to implement sparse fetching/pulling?
- From
Jonathan Nieder <jrnieder@gmail.com>
- Date
- Nov 30, 2017, 20:03 UTC
- Message-ID
- <20171130200341.GA20640@aiede.mtv.corp.google.com>
- In-Reply-To
- <CANxXvsO0xk3K8Wx9pmX1qST1=43BkrKWOcCZjJ8vVcBFYVRB0A@mail.gmail.com>
Hi Vitaly,
Vitaly Arbuzov wrote:
Show 6 quoted lines
> Found some details here: https://github.com/jeffhostetler/git/pull/3 > > Looking at commits I see that you've done a lot of work already, > including packing, filtering, fetching, cloning etc. > What are some areas that aren't complete yet? Do you need any help > with implementation?
That's a great question! I've filed https://crbug.com/git/2 to track this project. Feel free to star it to get updates there, or to add updates of your own.
As described at https://crbug.com/git/2#c1, currently there are three patch series for which review would be very welcome. Building on top of them is welcome as well. Please make sure to coordinate with jeffhost@microsoft.com and jonathantanmy@google.com (e.g. through the bug tracker or email).
One piece of missing functionality that looks intereseting to me: that series batches fetches of the missing blobs involved in a "git checkout" command:
https://public-inbox.org/git/20171121211528.21891-14-git@jeffhostetler.com/
But if doesn't batch fetches of the missing blobs involved in a "git diff <commit> <commit>" command. That might be a good place to get your hands dirty. :)
Thanks, Jonathan