Once using git clone —depth or git fetch —depth,
While you want to move backward.
you may face problem
git fetch --depth=105
error: Could not read 483bbf41ca5beb7e38b3b01f21149c56a1154b7a
error: Could not read aacb82de3ff8ae7b0a9e4cfec16c1807b6c315ef
error: Could not read 5a1758710d06ce9ddef754a8ee79408277032d8b
error: Could not read a7d5629fe0580bd3e154206388371f5b8fc832db
error: Could not read 073291c476b4edb4d10bbada1e64b471ba153b6b
On Nov 28, 2013, at 5:20 PM, Tay Ray Chuan <rcta...@gmail.com> wrote:
> On Thu, Nov 28, 2013 at 4:14 PM, Duy Nguyen <pclo...@gmail.com> wrote:
>> On Thu, Nov 28, 2013 at 2:41 PM, zhifeng hu <z...@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.
> Ray Chuan
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html