git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dingyuan Wang <abcdoyle888@gmail.com>
To: "Torsten Bögershausen" <tboegi@web.de>, git@vger.kernel.org
Subject: Re: assert failed in pathspec.c
Date: Thu, 11 Feb 2016 16:56:32 +0800	[thread overview]
Message-ID: <56BC4CC0.1090209@gmail.com> (raw)
In-Reply-To: <56BC4535.6070301@web.de>

git version 2.7.0.GIT (latest git master)

Sorry, I have found out that this problem is exactly the same as the
previous post I mentioned.

When I created the repo, scripts/ was a subrepo, and then I moved
scripts/.git out. If I add files in the scripts/ dir, SIGABRT.

在 2016年02月11日 16:24, Torsten Bögershausen 写道:
> On 02/11/2016 04:59 AM, Dingyuan Wang wrote:
> []
> 
> Thanks for the bug report.
> 
> What does
> git --version
> give you ?
> 
> And what happens, if you run the latest version of Git ?
> 

-- 
Dingyuan Wang

  reply	other threads:[~2016-02-11  8:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-11  3:59 assert failed in pathspec.c Dingyuan Wang
2016-02-11  8:24 ` Torsten Bögershausen
2016-02-11  8:56   ` Dingyuan Wang [this message]
2016-02-11 16:13 ` Junio C Hamano

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=56BC4CC0.1090209@gmail.com \
    --to=abcdoyle888@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=tboegi@web.de \
    /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).