From: Lars Schneider <larsxschneider@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: There are too many unreachable loose objects
Date: Fri, 9 Jun 2017 13:10:13 +0200 [thread overview]
Message-ID: <3C13D221-1F42-4012-914E-53634DD5BC79@gmail.com> (raw)
In-Reply-To: <20170609053643.k2skjxf55xtjty2q@sigill.intra.peff.net>
> On 09 Jun 2017, at 07:36, Jeff King <peff@peff.net> wrote:
>
> On Thu, Jun 08, 2017 at 02:52:42PM +0200, Lars Schneider wrote:
>
>>>> It may be that it's the server side that needs to git-prune, and not
>>>> your local side? I'm not really certain but you're doing a push which
>>>> talks to a remote server.
>>>
>>> Yes, certainly the position in the output implies that. These days you
>>> should see:
>>>
>>> remote: warning: There are too many...
>>>
>>> to make it more clear. Perhaps the server is too old to have 860a2ebec
>>> (receive-pack: send auto-gc output over sideband 2, 2016-06-05).
>>
>> Do you know if GHE 2.9.4 has this fix? (Is it OK to ask this here?)
>> Context: http://public-inbox.org/git/9C2F2EA2-0C59-4EA2-8C8E-10228FB82D90@gmail.com/
>
> It's probably not the best place to ask, as I don't think there is an
> easy way to find the answer unless you have the GHE source code. But the
> answer is no, it's in GHE 2.10.0.
OK!
> Actually, I guess you could run "git version" on the GHE box; the
> version numbers show the latest version of upstream Git that has been
> merged. This particular commit is in Git v2.10.0 (coincidental to the
> GHE version above; the versions are totally independent).
Thanks for the `git version` tip :-)
- Lars
prev parent reply other threads:[~2017-06-09 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 21:58 There are too many unreachable loose objects Hilco Wijbenga
2017-02-16 22:36 ` Jacob Keller
2017-02-16 22:57 ` Jeff King
2017-06-08 12:52 ` Lars Schneider
2017-06-09 5:36 ` Jeff King
2017-06-09 11:10 ` Lars Schneider [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C13D221-1F42-4012-914E-53634DD5BC79@gmail.com \
--to=larsxschneider@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).