From: Amit Walambe <awalambe@arcom.com>
To: git@vger.kernel.org
Cc: "Amit Walambe (awalambe@arcom.com)" <awalambe@arcom.com>
Subject: Re: git bisect not accepting -git kernels
Date: Tue, 17 Jul 2007 17:58:21 +0100 [thread overview]
Message-ID: <469CF52D.10407@arcom.com> (raw)
In-Reply-To: <469CF2E6.1020104@lsrfire.ath.cx>
Thanks a ton everyone for all the replies.
Here is the current status :
René Scharfe wrote:
> Amit Walambe schrieb:
>> Hi!
>> I was trying to do a git bisect on 2.6.22-git6 and 2.6.22-git8. For
>> which I get following error :
>> root@amit:/usr/src/linux-git # git bisect good v2.6.22-git6
>> Bad rev input: v2.6.22-git6
>
> The -git snapshots are made automatically by kernel.org, and their name
> is not included in the git repository. You could create tags for them
> like this:
>
> git tag v2.6.22-git6 8f41958bdd577731f7411c9605cfaa9db6766809
> git tag v2.6.22-git8 a5fcaa210626a79465321e344c91a6a7dc3881fa
>
> ... and afterwards you can use those revision names with bisect (or
> other git commands). I've got the commit IDs (i.e. those mysterious 40
> hex digits above) from the first line of the changelogs; their URLs are:
>
> http://kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.22-git6.log
> http://kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.22-git8.log
I found the commit ids in following file as well :
http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.22-git6.id
http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.22-git8.id
But telling good/bad points to git bisect still fails, whether I pass
the commit-id or the tags I created with commands given by René :
root@amit:/usr/src/linux-git # git bisect good
8f41958bdd577731f7411c9605cfaa9db6766809
cat: .git/BISECT_NAMES: No such file or directory
root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git # git tag v2.6.22-git6
8f41958bdd577731f7411c9605cfaa9db6766809
root@amit:/usr/src/linux-git # git tag v2.6.22-git8
a5fcaa210626a79465321e344c91a6a7dc3881fa
root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git # git bisect good v2.6.22-git6
cat: .git/BISECT_NAMES: No such file or directory
root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git #
root@amit:/usr/src/linux-git # git bisect bad v2.6.22-git8
cat: .git/BISECT_NAMES: No such file or directory
Thanks and Regards,
--
Amit Walambe
Design Engineer, Arcom Control Systems Ltd.
http://www.arcom.com
Tel: +44-(0)1223 411200 ext. 3204
Direct: +44-(0)1223 403465
_____________________________________________________________________
The message in this transmission is sent in confidence for the attention of the addressee only and should not be disclosed to any other party. Unauthorised recipients are requested to preserve this confidentiality. Please advise the sender if the addressee is not resident at the receiving end. Email to and from Arcom is automatically monitored for operational and lawful business reasons.
This message has been virus scanned by MessageLabs.
next prev parent reply other threads:[~2007-07-17 16:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 16:03 git bisect not accepting -git kernels Amit Walambe
2007-07-17 16:13 ` Peter Baumann
2007-07-17 16:16 ` Thomas Glanzmann
2007-07-17 16:36 ` Amit Walambe
2007-07-17 17:06 ` Amit Walambe
2007-07-17 16:44 ` Sam Ravnborg
2007-07-17 16:48 ` René Scharfe
2007-07-17 16:58 ` Amit Walambe [this message]
2007-07-17 17:10 ` Julian Phillips
2007-07-17 17:15 ` Amit Walambe
2007-07-17 17:11 ` Rogan Dawes
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=469CF52D.10407@arcom.com \
--to=awalambe@arcom.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 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).