From: Junio C Hamano <gitster@pobox.com>
To: Chris Packham <judge.packham@gmail.com>
Cc: GIT <git@vger.kernel.org>
Subject: Re: [bug] assertion in 2.8.4 triggering on old-ish worktree
Date: Thu, 16 Jun 2016 10:59:42 -0700 [thread overview]
Message-ID: <xmqqbn31581d.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAFOYHZArnE6vJ0U1zJAxytCBJJU5M-VtHbct6Qq4VPfw7-T-2A@mail.gmail.com> (Chris Packham's message of "Thu, 16 Jun 2016 17:02:02 +1200")
Chris Packham <judge.packham@gmail.com> writes:
> On Thu, Jun 16, 2016 at 4:59 PM, Chris Packham <judge.packham@gmail.com> wrote:
>> Hi All,
>>
>> I have the git-sh-prompt configured in my .bashrc today I visited an
>> old worktree that I haven't really touched in a few years (sorry can't
>> remember the git version I was using back then). I received the
>> following output when changing to the directory
>>
>> git: pathspec.c:317: prefix_pathspec: Assertion `item->nowildcard_len
>> <= item->len && item->prefix <= item->len' failed.
>>
>> I assume it's one of the git invocations in git-sh-prompt that's
>> hitting the assertion. Any thoughts on what might be triggering it?
>> Any debug I can gather?
>
> A bit more info. The directory in question is a uninitialised
> submodule. It doesn't trigger in the root of the parent project.
Sounds like
http://article.gmane.org/gmane.comp.version-control.git/283549
next prev parent reply other threads:[~2016-06-16 17:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 4:59 [bug] assertion in 2.8.4 triggering on old-ish worktree Chris Packham
2016-06-16 5:02 ` Chris Packham
2016-06-16 16:31 ` Stefan Beller
2016-06-16 16:55 ` Dennis Kaarsemaker
2016-06-16 16:59 ` Stefan Beller
2016-06-16 17:59 ` Junio C Hamano [this message]
2016-06-16 19:48 ` Stefan Beller
2016-06-17 2:41 ` Chris Packham
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=xmqqbn31581d.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=judge.packham@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.