From: "Trần Ngọc Quân" <vnwildman@gmail.com>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: How to repair a shallow clone (?)
Date: Sun, 07 Dec 2014 07:37:58 +0700 [thread overview]
Message-ID: <5483A166.4010109@gmail.com> (raw)
In-Reply-To: <5482F55F.1060008@web.de>
On 06/12/2014 19:23, Torsten Bögershausen wrote:
> 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.
next prev parent reply other threads:[~2014-12-07 0:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-06 12:23 How to repair a shallow clone (?) Torsten Bögershausen
2014-12-07 0:37 ` Trần Ngọc Quân [this message]
2014-12-07 11:05 ` Philip Oakley
2014-12-07 11:44 ` Duy Nguyen
2014-12-07 17:53 ` Torsten Bögershausen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5483A166.4010109@gmail.com \
--to=vnwildman@gmail.com \
--cc=git@vger.kernel.org \
--cc=tboegi@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).