All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Beller <stefanbeller@googlemail.com>
To: "Benoît Legat" <benoit.legat@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Bug with `git branch HEAD` in a 'detached HEAD' state
Date: Thu, 15 Aug 2013 22:58:17 +0200	[thread overview]
Message-ID: <520D40E9.1020000@googlemail.com> (raw)
In-Reply-To: <520D3F2A.5020203@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]

On 08/15/2013 10:50 PM, Benoît Legat wrote:
> Hello everyone,
> 
> I think I have just found a bug in Git which basically occurs when I run
> `git log HEAD` in a detached HEAD state.
> To reproduce it, just run
> $ git init
> ...
> $ touch tmp
> ...
> $ git add tmp
> $ git commit -m "tmp"
> ...
> $ git checkout <commit_sha>
> ...
> $ git branch HEAD
> Segmentation fault (core dumped)
> 
> My version of git is the following
> $ git --version
> git version 1.8.1.2
> 
> If that helps (and even if it doesn't actually), I'm running ubuntu
> 13.04 64-bit.
> 
> Benoît Legat
> -- 
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


This should be fixed by 8efb8899cfe866dddb3659b9e0a94232161db65e
(2013-02-23, branch: segfault fixes and validation)

I could reproduce with 1.8.1.2, but not on current master branch.
If this annoys you too much, please update your git version. ;)

Stefan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]

      reply	other threads:[~2013-08-15 20:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-15 20:50 Bug with `git branch HEAD` in a 'detached HEAD' state Benoît Legat
2013-08-15 20:58 ` Stefan Beller [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=520D40E9.1020000@googlemail.com \
    --to=stefanbeller@googlemail.com \
    --cc=benoit.legat@gmail.com \
    --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 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.