git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: How to repair a shallow clone (?)

From
Trần Ngọc Quân <vnwildman@gmail.com>
Date
Dec 7, 2014, 00:37 UTC
Message-ID
<5483A166.4010109@gmail.com>
In-Reply-To
<5482F55F.1060008@web.de>
On 06/12/2014 19:23, Torsten Bögershausen wrote:
Show 7 quoted lines
> I think I started to clone the repo in a shallow way
> (SparkleShare asked if I want to clone the complete history,
> and I probably answered "no" )
>
> Is there a way to repair this situation ?
> (Except doing a complete re-clone ?)
>

I think git don't accept push from shallow repo. I've ever encounter this problem. I UNshallow it, then every thing will work:

$ git fetch --unshallow origin

This command will convert a shallow repository to a complete one. See git-fetch(1) and git-clone(1).

I hope it helpful! Thanks,

-- 
Trần Ngọc Quân.
Previous: Torsten BögershausenNext: Philip Oakley
Message 2 of 5 in “How to repair a shallow clone (?)”
  1. Torsten BögershausenDec 6, 2014
  2. Trần Ngọc QuânDec 7, 2014
  3. Philip OakleyDec 7, 2014
  4. Duy NguyenDec 7, 2014
  5. Torsten BögershausenDec 7, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.