{"thread":{"id":"45156","subject":"There are too many unreachable loose objects","startedAt":"2017-02-16T21:58:42Z","lastAt":"2017-06-09T11:10:21Z","messageCount":6,"participants":["Hilco Wijbenga","Jacob Keller","Jeff King","Lars Schneider"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"311815","messageId":"CAE1pOi3bpL0zTS9w2QCOrXcWk5pHj=xthxo2nYi8KEwJ=TgXfA@mail.gmail.com","threadId":"45156","inReplyTo":null,"subject":"There are too many unreachable loose objects","fromName":"Hilco Wijbenga","fromEmail":"hilco.wijbenga@gmail.com","sentAt":"2017-02-16T21:58:14Z","receivedAt":"2017-02-16T21:58:42Z","isPatch":false,"sender":{"key":"hilco.wijbenga@gmail.com","avatar":null},"body":"Hi all,\n\nWhenever I run \"git push --force(-with-lease)\" I get a variation of\n\nCounting objects: 187, done.\nDelta compression using up to 12 threads.\nCompressing objects: 100% (126/126), done.\nWriting objects: 100% (187/187), 21.35 KiB | 0 bytes/s, done.\nTotal 187 (delta 78), reused 71 (delta 20)\nwarning: There are too many unreachable loose objects; run 'git prune'\nto remove them.\nTo git@git.company.com:project.git\n + 51338ea...b0ebe39 my-branch -> my-branch (forced update)\n\nSo I'll run \"git prune\" and, for good measure, \"git gc\" (which even\nincludes \"git prune\"?). The first seems to do nothing, the latter does\nits thing.\n\nAnd then the next time (which could be a few minutes later) I get the\nsame warning. My branches aren't that big, the largest ever had 40-ish\ncommits. So abandoning a few dozen commits should not lead to this\nwarning, I would think.\n\nWhat am I doing wrong?\n\nCheers,\nHilco\n"},{"id":"311818","messageId":"CA+P7+xqWoUBOoFSiOTT5U-9aoqESUMnZeSGfvhGte2LqF18gmw@mail.gmail.com","threadId":"45156","inReplyTo":"CAE1pOi3bpL0zTS9w2QCOrXcWk5pHj=xthxo2nYi8KEwJ=TgXfA@mail.gmail.com","subject":"Re: There are too many unreachable loose objects","fromName":"Jacob Keller","fromEmail":"jacob.keller@gmail.com","sentAt":"2017-02-16T22:36:10Z","receivedAt":"2017-02-16T22:36:36Z","isPatch":false,"sender":{"key":"jacob.keller@gmail.com","avatar":"https://avatars.githubusercontent.com/u/874719?v=4"},"body":"On Thu, Feb 16, 2017 at 1:58 PM, Hilco Wijbenga\n<hilco.wijbenga@gmail.com> wrote:\n> Hi all,\n>\n> Whenever I run \"git push --force(-with-lease)\" I get a variation of\n>\n> Counting objects: 187, done.\n> Delta compression using up to 12 threads.\n> Compressing objects: 100% (126/126), done.\n> Writing objects: 100% (187/187), 21.35 KiB | 0 bytes/s, done.\n> Total 187 (delta 78), reused 71 (delta 20)\n> warning: There are too many unreachable loose objects; run 'git prune'\n> to remove them.\n> To git@git.company.com:project.git\n>  + 51338ea...b0ebe39 my-branch -> my-branch (forced update)\n>\n> So I'll run \"git prune\" and, for good measure, \"git gc\" (which even\n> includes \"git prune\"?). The first seems to do nothing, the latter does\n> its thing.\n>\n\nIt may be that it's the server side that needs to git-prune, and not\nyour local side? I'm not really certain but you're doing a push which\ntalks to a remote server.\n\nThanks,\nJake\n\n> And then the next time (which could be a few minutes later) I get the\n> same warning. My branches aren't that big, the largest ever had 40-ish\n> commits. So abandoning a few dozen commits should not lead to this\n> warning, I would think.\n>\n> What am I doing wrong?\n>\n> Cheers,\n> Hilco\n"},{"id":"311822","messageId":"20170216225710.6nnbw65qoeb6lrw5@sigill.intra.peff.net","threadId":"45156","inReplyTo":"CA+P7+xqWoUBOoFSiOTT5U-9aoqESUMnZeSGfvhGte2LqF18gmw@mail.gmail.com","subject":"Re: There are too many unreachable loose objects","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2017-02-16T22:57:10Z","receivedAt":"2017-02-16T22:57:17Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Thu, Feb 16, 2017 at 02:36:10PM -0800, Jacob Keller wrote:\n\n> > Whenever I run \"git push --force(-with-lease)\" I get a variation of\n> >\n> > Counting objects: 187, done.\n> > Delta compression using up to 12 threads.\n> > Compressing objects: 100% (126/126), done.\n> > Writing objects: 100% (187/187), 21.35 KiB | 0 bytes/s, done.\n> > Total 187 (delta 78), reused 71 (delta 20)\n> > warning: There are too many unreachable loose objects; run 'git prune'\n> > to remove them.\n> > To git@git.company.com:project.git\n> >  + 51338ea...b0ebe39 my-branch -> my-branch (forced update)\n> >\n> > So I'll run \"git prune\" and, for good measure, \"git gc\" (which even\n> > includes \"git prune\"?). The first seems to do nothing, the latter does\n> > its thing.\n> >\n> \n> It may be that it's the server side that needs to git-prune, and not\n> your local side? I'm not really certain but you're doing a push which\n> talks to a remote server.\n\nYes, certainly the position in the output implies that. These days you\nshould see:\n\n  remote: warning: There are too many...\n\nto make it more clear. Perhaps the server is too old to have 860a2ebec\n(receive-pack: send auto-gc output over sideband 2, 2016-06-05).\n\n-Peff\n"},{"id":"321752","messageId":"987153C6-2F10-4229-8E59-B106604896DF@gmail.com","threadId":"45156","inReplyTo":"20170216225710.6nnbw65qoeb6lrw5@sigill.intra.peff.net","subject":"Re: There are too many unreachable loose objects","fromName":"Lars Schneider","fromEmail":"larsxschneider@gmail.com","sentAt":"2017-06-08T12:52:42Z","receivedAt":"2017-06-08T12:52:50Z","isPatch":false,"sender":{"key":"larsxschneider@gmail.com","avatar":"https://avatars.githubusercontent.com/u/477434?v=4"},"body":"\n> On 16 Feb 2017, at 23:57, Jeff King <peff@peff.net> wrote:\n> \n> On Thu, Feb 16, 2017 at 02:36:10PM -0800, Jacob Keller wrote:\n> \n>>> Whenever I run \"git push --force(-with-lease)\" I get a variation of\n>>> \n>>> Counting objects: 187, done.\n>>> Delta compression using up to 12 threads.\n>>> Compressing objects: 100% (126/126), done.\n>>> Writing objects: 100% (187/187), 21.35 KiB | 0 bytes/s, done.\n>>> Total 187 (delta 78), reused 71 (delta 20)\n>>> warning: There are too many unreachable loose objects; run 'git prune'\n>>> to remove them.\n>>> To git@git.company.com:project.git\n>>> + 51338ea...b0ebe39 my-branch -> my-branch (forced update)\n>>> \n>>> So I'll run \"git prune\" and, for good measure, \"git gc\" (which even\n>>> includes \"git prune\"?). The first seems to do nothing, the latter does\n>>> its thing.\n>>> \n>> \n>> It may be that it's the server side that needs to git-prune, and not\n>> your local side? I'm not really certain but you're doing a push which\n>> talks to a remote server.\n> \n> Yes, certainly the position in the output implies that. These days you\n> should see:\n> \n>  remote: warning: There are too many...\n> \n> to make it more clear. Perhaps the server is too old to have 860a2ebec\n> (receive-pack: send auto-gc output over sideband 2, 2016-06-05).\n\nDo you know if GHE 2.9.4 has this fix? (Is it OK to ask this here?)\nContext: http://public-inbox.org/git/9C2F2EA2-0C59-4EA2-8C8E-10228FB82D90@gmail.com/\n\nThanks,\nLars"},{"id":"321814","messageId":"20170609053643.k2skjxf55xtjty2q@sigill.intra.peff.net","threadId":"45156","inReplyTo":"987153C6-2F10-4229-8E59-B106604896DF@gmail.com","subject":"Re: There are too many unreachable loose objects","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2017-06-09T05:36:44Z","receivedAt":"2017-06-09T05:36:53Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Thu, Jun 08, 2017 at 02:52:42PM +0200, Lars Schneider wrote:\n\n> >> It may be that it's the server side that needs to git-prune, and not\n> >> your local side? I'm not really certain but you're doing a push which\n> >> talks to a remote server.\n> > \n> > Yes, certainly the position in the output implies that. These days you\n> > should see:\n> > \n> >  remote: warning: There are too many...\n> > \n> > to make it more clear. Perhaps the server is too old to have 860a2ebec\n> > (receive-pack: send auto-gc output over sideband 2, 2016-06-05).\n> \n> Do you know if GHE 2.9.4 has this fix? (Is it OK to ask this here?)\n> Context: http://public-inbox.org/git/9C2F2EA2-0C59-4EA2-8C8E-10228FB82D90@gmail.com/\n\nIt's probably not the best place to ask, as I don't think there is an\neasy way to find the answer unless you have the GHE source code. But the\nanswer is no, it's in GHE 2.10.0.\n\nActually, I guess you could run \"git version\" on the GHE box; the\nversion numbers show the latest version of upstream Git that has been\nmerged. This particular commit is in Git v2.10.0 (coincidental to the\nGHE version above; the versions are totally independent).\n\n-Peff\n"},{"id":"321822","messageId":"3C13D221-1F42-4012-914E-53634DD5BC79@gmail.com","threadId":"45156","inReplyTo":"20170609053643.k2skjxf55xtjty2q@sigill.intra.peff.net","subject":"Re: There are too many unreachable loose objects","fromName":"Lars Schneider","fromEmail":"larsxschneider@gmail.com","sentAt":"2017-06-09T11:10:13Z","receivedAt":"2017-06-09T11:10:21Z","isPatch":false,"sender":{"key":"larsxschneider@gmail.com","avatar":"https://avatars.githubusercontent.com/u/477434?v=4"},"body":"\n> On 09 Jun 2017, at 07:36, Jeff King <peff@peff.net> wrote:\n> \n> On Thu, Jun 08, 2017 at 02:52:42PM +0200, Lars Schneider wrote:\n> \n>>>> It may be that it's the server side that needs to git-prune, and not\n>>>> your local side? I'm not really certain but you're doing a push which\n>>>> talks to a remote server.\n>>> \n>>> Yes, certainly the position in the output implies that. These days you\n>>> should see:\n>>> \n>>> remote: warning: There are too many...\n>>> \n>>> to make it more clear. Perhaps the server is too old to have 860a2ebec\n>>> (receive-pack: send auto-gc output over sideband 2, 2016-06-05).\n>> \n>> Do you know if GHE 2.9.4 has this fix? (Is it OK to ask this here?)\n>> Context: http://public-inbox.org/git/9C2F2EA2-0C59-4EA2-8C8E-10228FB82D90@gmail.com/\n> \n> It's probably not the best place to ask, as I don't think there is an\n> easy way to find the answer unless you have the GHE source code. But the\n> answer is no, it's in GHE 2.10.0.\n\nOK!\n\n> Actually, I guess you could run \"git version\" on the GHE box; the\n> version numbers show the latest version of upstream Git that has been\n> merged. This particular commit is in Git v2.10.0 (coincidental to the\n> GHE version above; the versions are totally independent).\n\nThanks for the `git version` tip :-)\n\n- Lars\n"}]}