From: Mike Hommey <mh@glandium.org>
To: git@vger.kernel.org
Subject: [Crash] git-push $remote $non_ref:$anything
Date: Sun, 15 Jun 2008 21:38:23 +0200 [thread overview]
Message-ID: <20080615193823.GA11218@glandium.org> (raw)
Hi,
I somehow managed to get a segfault by running this:
git push origin non-existant-branch-name:non-existant-branch-name
FWIW, the output looks like this:
error: src refspec patches/uri-handlers does not match any.
Segmentation fault
fatal: The remote end hung up unexpectedly
I don't have time to dig into this, unfortunately.
Mike
next reply other threads:[~2008-06-15 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-15 19:38 Mike Hommey [this message]
2008-06-15 19:55 ` [Crash] git-push $remote $non_ref:$anything Jeff King
2008-06-15 21:06 ` Daniel Barkalow
2008-06-16 16:15 ` Jeff King
2008-06-16 16: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=20080615193823.GA11218@glandium.org \
--to=mh@glandium.org \
--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