From: Jeff King <peff@peff.net>
To: Elijah Newren <newren@gmail.com>
Cc: "Stefan Beller" <sbeller@google.com>,
"Git Mailing List" <git@vger.kernel.org>,
"Nguyễn Thái Ngọc" <pclouds@gmail.com>
Subject: Re: BUG: fetch in certain repo always gives "did not send all necessary objects"
Date: Wed, 7 Feb 2018 08:25:11 -0500 [thread overview]
Message-ID: <20180207132511.GA19396@sigill.intra.peff.net> (raw)
In-Reply-To: <20180207132157.GB16018@sigill.intra.peff.net>
On Wed, Feb 07, 2018 at 08:21:57AM -0500, Jeff King wrote:
> The best PSA for this particular bug may be "try pruning the worktrees":
>
> $ git worktree prune -v
> Removing worktrees/foo: gitdir file points to non-existent location
>
> $ git prune; echo $?
> 0
Sorry, I just read Stefan's response and not your original before
responding. I see that you did try that. So IMHO that's a separate bug
that "worktree prune" did not do the right thing for your particular
case.
-Peff
next prev parent reply other threads:[~2018-02-07 13:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 23:04 BUG: fetch in certain repo always gives "did not send all necessary objects" Elijah Newren
2018-02-06 23:20 ` Stefan Beller
2018-02-07 0:00 ` Elijah Newren
2018-02-07 11:08 ` Duy Nguyen
2018-02-07 13:23 ` Jeff King
2018-02-07 18:12 ` Elijah Newren
2018-02-07 13:21 ` Jeff King
2018-02-07 13:25 ` Jeff King [this message]
2018-02-07 17:25 ` Elijah Newren
2018-02-07 18:17 ` Jeff King
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=20180207132511.GA19396@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
--cc=pclouds@gmail.com \
--cc=sbeller@google.com \
/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).