From: Ryan Anderson <ryan@michonline.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: git-bisect problem
Date: Mon, 13 Feb 2006 04:39:38 -0500 [thread overview]
Message-ID: <20060213093938.GC11053@mythryan2.michonline.com> (raw)
In-Reply-To: <20060213013205.4ba47836.akpm@osdl.org>
On Mon, Feb 13, 2006 at 01:32:05AM -0800, Andrew Morton wrote:
> Junio C Hamano <junkio@cox.net> wrote:
> >
> > As humans, we can tell that it is not very plausible that the
> > EXTRAVERSION change caused whatever breakage you are chasing,
> > but sorry, from your log, I think bisect is doing the right
> > thing.
>
> I don't think humans are well-suited to using git.
>
> My current theory is that I was bisecting Linus's tree all along.
>
> What is the correct way in which to switch to git-netdev-all in preparation
> for performing the bisection?
First, use "git branch" to show you what branches exist, the * will mark
the current one.
Then "git checkout $branch" to switch to one that exists, or "git
checkout -b $newbranch $sourcebranch" to create a new branch starting
from $sourcebranch (which can also be a random commit/tag/etc).
--
Ryan Anderson
sometimes Pug Majere
next prev parent reply other threads:[~2006-02-13 9:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 8:25 git-bisect problem Andrew Morton
2006-02-13 9:11 ` Junio C Hamano
2006-02-13 9:32 ` Andrew Morton
2006-02-13 9:39 ` Ryan Anderson [this message]
2006-02-13 9:51 ` Andrew Morton
2006-02-13 9:58 ` Fernando J. Pereda
2006-02-13 10:22 ` Luben Tuikov
2006-02-13 10:23 ` Luben Tuikov
2006-02-13 12:21 ` cat-file (was Re: git-bisect problem) Joshua N Pritikin
2006-02-13 10:14 ` git-bisect problem Ryan Anderson
2006-02-13 10:25 ` Andrew Morton
2006-02-13 16:44 ` Linus Torvalds
2006-02-13 10:40 ` Luben Tuikov
2006-02-13 10:44 ` Andrew Morton
2006-02-14 0:33 ` Junio C Hamano
2006-02-13 10:08 ` Junio C Hamano
2006-02-13 10:19 ` Andrew Morton
2006-02-14 0:32 ` Junio C Hamano
2006-02-14 0:56 ` Andrew Morton
2006-02-14 1:14 ` Linus Torvalds
2006-02-14 1:15 ` Petr Baudis
2006-02-14 1:27 ` Petr Baudis
2006-02-14 1:52 ` Junio C Hamano
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=20060213093938.GC11053@mythryan2.michonline.com \
--to=ryan@michonline.com \
--cc=akpm@osdl.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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.