From: Junio C Hamano <junkio@cox.net>
To: walt <wa1ter@myrealbox.com>
Cc: git@vger.kernel.org
Subject: Re: Real-life kernel debugging scenario
Date: Mon, 07 Nov 2005 17:30:18 -0800 [thread overview]
Message-ID: <7vwtjkncyd.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <dkosr7$f4s$1@sea.gmane.org> (wa1ter@myrealbox.com's message of "Mon, 07 Nov 2005 16:51:50 -0800")
walt <wa1ter@myrealbox.com> writes:
> First: is this an optimal tactic?
Not if you are a git user.
> Second: how to back out individual commits using git or
> cogito? I suppose this is already spelled out in the docs,
> but I invite everyone to point me to the relevant places
> in the docs that have escaped my attention so far.
git-bisect(1).
next prev parent reply other threads:[~2005-11-08 1:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 0:51 Real-life kernel debugging scenario walt
2005-11-08 0:59 ` David Lang
2005-11-08 1:30 ` Junio C Hamano [this message]
2005-11-08 1:31 ` Linus Torvalds
2005-11-09 17:40 ` wa1ter
2005-11-09 18:17 ` Jon Loeliger
2005-11-09 18:36 ` Linus Torvalds
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=7vwtjkncyd.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=wa1ter@myrealbox.com \
/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).