From: Olaf Hering <olh@suse.de>
To: Junio C Hamano <junkio@cox.net>, pasky@suse.cz
Cc: git@vger.kernel.org,
Uwe Zeisberger <zeisberg@informatik.uni-freiburg.de>
Subject: Re: git-bisect broken in 1.2.4
Date: Tue, 2 May 2006 09:33:04 +0200 [thread overview]
Message-ID: <20060502073304.GA26111@suse.de> (raw)
In-Reply-To: <7vpsiwopkv.fsf@assigned-by-dhcp.cox.net>
On Tue, May 02, Junio C Hamano wrote:
> Uwe Zeisberger <zeisberg@informatik.uni-freiburg.de> writes:
>
> > Olaf Hering wrote:
> >> Did SuSE just pick up a bad version of git, 1.2.4?
> >> git-bisect doesnt work correctly in the kernel sources, .git/HEAD doesnt
> >> contain the commit id anymore, but 'ref: refs/heads/bisect'
> >>
> >> CONFIG_LOCALVERSION_AUTO depends on the id.
> > Probably you should update to at least linux-v2.6.15-g117a93d. The
> > script to determine the localversion[1] depends on .git/HEAD being a
> > symlink.
> >
> > Since
> >
> > git-1.1.4-g2fabd21
> >
> > .git/HEAD isn't a symlink any more (per default at least).
>
> Ouch. Although what Uwe says is all correct, we should not say
> "don't try kernel older than 2615-117a". That makes bisect
> rather useless.
>
> > You can rebuild git with USE_SYMLINK_HEAD if you really want the old
> > behaviour.
>
> That probably is a sane thing to do.
Ok, thanks for the patch.
Petr, can you update our git package in time?
next prev parent reply other threads:[~2006-05-02 7:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-01 18:10 git-bisect broken in 1.2.4 Olaf Hering
2006-05-02 7:01 ` Uwe Zeisberger
2006-05-02 7:25 ` Junio C Hamano
2006-05-02 7:33 ` Olaf Hering [this message]
2006-05-02 10:42 ` Johannes Schindelin
[not found] ` <7vslnskzjj.fsf@assigned-by-dhcp.cox.net>
2006-05-02 19:38 ` Johannes Schindelin
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=20060502073304.GA26111@suse.de \
--to=olh@suse.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=pasky@suse.cz \
--cc=zeisberg@informatik.uni-freiburg.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 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.