git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ralf Wildenhues" <Ralf.Wildenhues@gmx.de>
To: Ingo Molnar <mingo@elte.hu>, git@vger.kernel.org
Cc: Jan Beulich <JBeulich@novell.com>,
	"H.J. Lu" <hjl.tools@gmail.com>,
	binutils@sourceware.org, linux-kernel@vger.kernel.org,
	"H. Peter Anvin" <hpa@zytor.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: git bisect plus fixes (was: PATCH: Add --size-check=[error|warning])
Date: Mon, 14 Mar 2011 14:16:23 +0100	[thread overview]
Message-ID: <20110314131623.119020@gmx.net> (raw)
In-Reply-To: <20110314122342.GA26825@elte.hu>

[ adding the git list; this is
  http://thread.gmane.org/gmane.comp.gnu.binutils/52601/focus=1112779 ]

Hello,

* Ingo Molnar wrote on Mon, Mar 14, 2011 at 01:23:42PM CET:
> Also, i hope you are not suggesting to break projects just because
> they are not important to you personally? The fix is exceedingly
> simple to do for the binutils project - and impossible to do for the
> kernel project (because during bisection - which is a very powerful
> debugging tool - older versions of the source get checked out).

FWIW, I don't have an opinion on this particular binutils issue, but
it would be very helpful if 'git bisect' made it easy to denote
"when going back, you might also need some of these changes".
(I'd just use a patch -p1 with a here-file in the bisect script, but
that might not be enough for all practical use cases.)

This issue has come up several times with high-profile issues.

Thanks,
Ralf

       reply	other threads:[~2011-03-14 13:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110311165802.GA3508@intel.com>
     [not found] ` <4D7A64670200007800035F4C@vpn.id2.novell.com>
     [not found]   ` <AANLkTikG8wa1Em0bEUddbYpYs2TzFFTDb95qWFJ3xSbv@mail.gmail.com>
     [not found]     ` <4D7DE39302000078000362E6@vpn.id2.novell.com>
     [not found]       ` <20110314095534.GB18058@elte.hu>
     [not found]         ` <20110314104131.GG6275@bubble.grove.modra.org>
     [not found]           ` <20110314122342.GA26825@elte.hu>
2011-03-14 13:16             ` Ralf Wildenhues [this message]
2011-03-14 13:47               ` [PATCH] git-bisect.txt: example for bisecting with hotfix Michael J Gruber
2011-03-14 17:35                 ` Junio C Hamano
2011-03-15 21:24                   ` [PATCHv2 1/2] git-bisect.txt: streamline run presentation Michael J Gruber
2011-03-15 21:24                     ` [PATCHv2 2/2] git-bisect.txt: example for bisecting with hot-fix Michael J Gruber
2011-03-14 21:00               ` [PATCH] Document 'git bisect fix' Ralf Wildenhues
2011-03-15 10:16                 ` Yann Dirson
2011-03-16  9:52                 ` Christian Couder
2011-03-16 11:47                   ` Michael J Gruber
2011-03-16 20:35                     ` 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=20110314131623.119020@gmx.net \
    --to=ralf.wildenhues@gmx.de \
    --cc=JBeulich@novell.com \
    --cc=akpm@linux-foundation.org \
    --cc=binutils@sourceware.org \
    --cc=git@vger.kernel.org \
    --cc=hjl.tools@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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).