git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: Amit Walambe <awalambe@arcom.com>
Cc: git@vger.kernel.org
Subject: Re: git bisect not accepting -git kernels
Date: Tue, 17 Jul 2007 18:48:38 +0200	[thread overview]
Message-ID: <469CF2E6.1020104@lsrfire.ath.cx> (raw)
In-Reply-To: <469CE836.6010508@arcom.com>

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 repository is obtained by :
> root@amit:/usr/src # git clone
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6 linux-git
> 
> I am running following git version on Debian Sid, updated today.
> # git --version
> git version 0.99.8.GIT
> '# dpkg -l | grep git' shows ' git-core 1:1.5.2.3-1'
> 
> I tried searching man-pages/documentation/website but couldn't find any
> references to git bisect on -git kernels. I would be grateful if anyone
> can help me find what's going wrong.

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

René

  parent reply	other threads:[~2007-07-17 16:48 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 [this message]
2007-07-17 16:58   ` Amit Walambe
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=469CF2E6.1020104@lsrfire.ath.cx \
    --to=rene.scharfe@lsrfire.ath.cx \
    --cc=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).