From: Yann Dirson <dirson@bertin.fr>
To: Michael J Gruber <git@drmicha.warpmail.net>,
Christian Couder <christian.couder@gmail.com>,
Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Cc: git list <git@vger.kernel.org>
Subject: Re: [PATCH] Document 'git bisect fix'.
Date: Wed, 16 Mar 2011 14:34:02 +0100 [thread overview]
Message-ID: <20110316143402.69e66f16@chalon.bertin.fr> (raw)
>I'd say the replace method is perfect for transporting an existing fix
>"back in time" when the range of non-bisectable commits is limited. But
>since you have to replace the right (most recent) commit in that range
>it is less convenient when you have a fix due to a changed/exotic build
>environment or such which you do not want in your mainline.
>
>Also, you have to rebase the whole history back to the commit which
>introduced the problem
Right, and that makes it much more difficult when you want to be
selective about which fixes you want to apply.
--
Yann Dirson - Bertin Technologies
next reply other threads:[~2011-03-16 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 13:34 Yann Dirson [this message]
[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 ` git bisect plus fixes (was: PATCH: Add --size-check=[error|warning]) Ralf Wildenhues
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=20110316143402.69e66f16@chalon.bertin.fr \
--to=dirson@bertin.fr \
--cc=Ralf.Wildenhues@gmx.de \
--cc=christian.couder@gmail.com \
--cc=git@drmicha.warpmail.net \
--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).