Re: How to resume broke clone ?
- From
Tay Ray Chuan <rctay89@gmail.com>
- Date
- Nov 28, 2013, 09:20 UTC
- Message-ID
- <CALUzUxrEvuKuN+v-hJLQd5KoV-fzxVYvg5pj7XoLBVap7mgA=Q@mail.gmail.com>
- In-Reply-To
- <CACsJy8DbJZmBCnfzNqfmEnRpqVcc42Q_-jz3r=sYVRPhsCkS5A@mail.gmail.com>
On Thu, Nov 28, 2013 at 4:14 PM, Duy Nguyen <pclouds@gmail.com> wrote:
Show 5 quoted lines
> On Thu, Nov 28, 2013 at 2:41 PM, zhifeng hu <zf@ancientrocklab.com> wrote: >> Thanks for reply, But I am developer, I want to clone full repository, I need to view code since very early. > > if it works with --depth =1, you can incrementally run "fetch > --depth=N" with N larger and larger.
I second Duy Nguyen's and Trần Ngọc Quân's suggestion to 1) initially create a "shallow" clone then 2) incrementally deepen your clone.
Zhifeng, in the course of your research into resumable cloning, you might have learnt that while it's a really valuable feature, it's also a pretty hard problem at the same time. So it's not because git doesn't want to have this feature.
-- Cheers, Ray Chuan