git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rémi Galan Alfonso" <remi.galanalfonso@almacam.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: RE: Segfault on git for Windows
Date: Wed, 5 Apr 2017 09:17:05 +0000	[thread overview]
Message-ID: <d7257257ee1047b4aefdede494df70b0@almacam.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1704051057150.4268@virtualbox>

> Hi Rémi,
> 
> On Wed, 5 Apr 2017, Rémi Galan Alfonso wrote:
> 
> > At $DAYWORK, the code is versionned under SVN. Since I haven't used SVN
> > before and try to have a clean and bisectable history, I installed git
> > with the intent to manage my code locally before pushing to SVN when I'm
> > satisfied (I haven't tries git-svn because I have never used it and
> > would like to avoid screwing up the SVN repo by some mistake).
> > 
> > So first to setup the local repo, I wanted to add all of the code files.
> > So I first ran at the root of the repo:
> >   $ git add ./**.cpp
> > Which is quite a big amount of files (partly because of external
> > dependencies which would have been smart to exclude, but it's done).
> >   $ find -type f -name "**.cpp" | wc -l
> >   8676
> > This command worked (return status is 0 and no error message).
> > 
> > However following `git add **.hpp` and `git status` segfault with no
> > additional message:
> >   $ git status
> >   Segmentation fault
> 
> I think this is the problem identified in
> https://github.com/git-for-windows/git/issues/1111.
> 
> To verify, you could try the snapshot (with the proposed fix) hosted here:
> http://wingit.blob.core.windows.net/files/index.html

Thanks, it fixed it. Sorry for the noise.
Rémi

      reply	other threads:[~2017-04-05  9:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05  7:38 Segfault on git for Windows Rémi Galan Alfonso
2017-04-05  8:58 ` Johannes Schindelin
2017-04-05  9:17   ` Rémi Galan Alfonso [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d7257257ee1047b4aefdede494df70b0@almacam.com \
    --to=remi.galanalfonso@almacam.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    /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).