From: Mark Hounschell <markh@compro.net>
To: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: kernel git bisect question
Date: Thu, 10 Mar 2011 15:27:00 -0500 [thread overview]
Message-ID: <4D793414.4090206@compro.net> (raw)
Between git bisect [good | bad ]s should I always "make clean" or can I
count on the build system to take care of everything properly?
Thanks
Mark
next reply other threads:[~2011-03-10 20:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 20:27 Mark Hounschell [this message]
2011-03-10 21:14 ` kernel git bisect question Sam Ravnborg
2011-03-10 21:17 ` Mark Hounschell
2011-03-10 21:54 ` Steven Rostedt
2011-03-11 18:31 ` Mark Hounschell
2011-03-11 18:37 ` Sam Ravnborg
2011-03-11 18:41 ` Mark Hounschell
2011-03-11 18:51 ` Steven Rostedt
2011-03-11 18:56 ` Mark Hounschell
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=4D793414.4090206@compro.net \
--to=markh@compro.net \
--cc=linux-kernel@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 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.