From: Trần Ngọc Quân vnwild...@gmail.com
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
On Sat, Dec 6, 2014 at 7:23 PM, Torsten Bögershausen tbo...@web.de wrote:
I share a bare repo with Sparkleshare which does an auto-synch.
Now the synch had stopped, and trying to push to the central repo
by hand gives this:
git push origin master
fatal: protocol error: expected
On 2014-12-07 12.44, Duy Nguyen wrote:
Is this a known issue/problem ?
No.
Thanks everybody for the support.
The machine was equipped with git version 1.7.10.4 in /usr/bin.
I installed 2.1 or so under /usr/local/bin, (and even /root/bin)
thinking that this would help, but it didn't.
I share a bare repo with Sparkleshare which does an auto-synch.
Now the synch had stopped, and trying to push to the central repo
by hand gives this:
git push origin master
fatal: protocol error: expected old/new/ref, got 'shallow
72fb4080921221293e28a97a0e8c78d6100c5186'
fatal: The remote
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
5 matches
Mail list logo