On 8 December 2016 at 14:18, Lars Schneider wrote:
>
>> On 08 Dec 2016, at 15:00, Nick Warr wrote:
>>
>> That looks pretty much like the error we're dealing with, any reason
>> why going back a point version on Git (not git-lfs) would resolve the
>> issue however?
>
> Going back to GitLFS 1.4.* w
> On 08 Dec 2016, at 15:00, Nick Warr wrote:
>
> That looks pretty much like the error we're dealing with, any reason
> why going back a point version on Git (not git-lfs) would resolve the
> issue however?
Going back to GitLFS 1.4.* would make the error disappear. However, I think
you should f
That looks pretty much like the error we're dealing with, any reason
why going back a point version on Git (not git-lfs) would resolve the
issue however?
On 8 December 2016 at 13:57, Lars Schneider wrote:
>
>> On 08 Dec 2016, at 12:46, Nick Warr wrote:
>>
>> Using Git-2.11.0 with the latest git-
> On 08 Dec 2016, at 12:46, Nick Warr wrote:
>
> Using Git-2.11.0 with the latest git-lfs 1.5.2 (also tested with
> 1.5.3) cloning from our locally hosted gitlab CE server via HTTPS.
>
> When cloning a repo (large, 3.3 gig in git, 10.3 in LFS) for the
> first time the clone will finish the che
Using Git-2.11.0 with the latest git-lfs 1.5.2 (also tested with
1.5.3) cloning from our locally hosted gitlab CE server via HTTPS.
When cloning a repo (large, 3.3 gig in git, 10.3 in LFS) for the
first time the clone will finish the checkout of the git part, then
when it starts downloading the
5 matches
Mail list logo
