From: Jiri Olsa <jolsa@redhat.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [BUG] git crash for git remote update tip tip
Date: Sun, 11 Dec 2016 14:50:57 +0100 [thread overview]
Message-ID: <20161211135057.GA32029@krava> (raw)
In-Reply-To: <20161211125116.xsabnud5tfwadndt@sigill.intra.peff.net>
On Sun, Dec 11, 2016 at 07:51:16AM -0500, Jeff King wrote:
> On Sun, Dec 11, 2016 at 01:17:44PM +0100, Jiri Olsa wrote:
>
> > I accidentaly added 2 remotes and git remote update
> > crashed, see the attached output.
> >
> > [jolsa@krava perf]$ git --version
> > git version 2.7.4
>
> This is fixed already by b7410f616 (builtin/fetch.c: don't free
> remote->name after fetch, 2016-06-14), which is in v2.9.1.
ugh, time to update my fedora ;-)
thanks,
jirka
prev parent reply other threads:[~2016-12-11 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 12:17 [BUG] git crash for git remote update tip tip Jiri Olsa
2016-12-11 12:51 ` Jeff King
2016-12-11 13:50 ` Jiri Olsa [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=20161211135057.GA32029@krava \
--to=jolsa@redhat.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).