Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

11
  • 25
    This is the only answer that describes a workaround for the problem without switching to SSH. This worked for me, thanks! Commented Jul 10, 2017 at 14:36
  • 30
    The key here is --depth 1 and --unshallow. This also works for fetching an existing repo on slow connection: git fetch --depth 1 then git fetch --unshallow. Commented Feb 13, 2018 at 9:10
  • 8
    Now, the git fetch --unshallow command give RPC failed; error Commented Jul 5, 2019 at 12:25
  • 4
    Didn't work for me. Failed on the git fetch --unshallow. Guess my repo is too big even for this approach. Only SSH worked. Commented Feb 14, 2020 at 22:48
  • 21
    If git fetch --unshallow still reports errors, you can use git fetch --depth=100 and then git fetch --depth=200 and then git fetch --depth=300 and so on to fetch repo incrementally. This way works for Linux kernel repo, which is extremely large. Commented Jun 2, 2020 at 5:19