From: Jiri Kosina <jkosina@suse.cz>
To: NeilBrown <neilb@suse.de>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TOPIC] Metadata addendum to git commit
Date: Wed, 14 May 2014 01:29:29 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.1405140127240.16459@pobox.suse.cz> (raw)
In-Reply-To: <20140514092340.24ab4c9e@notabene.brown>
On Wed, 14 May 2014, NeilBrown wrote:
> A particular practical issue is that when doing a git-bisect there might
> be a range of commits that only compile/run if some later commit is
> applied. If I'm bisecting in that range, I have to repeatedly apply that
> commit by hand.
You can just have it stored in a separate branch and perform the bisection
using a script that will always first merge the branch, and reset after
good/bad verification is done.
If the fix is already applied (because you are testing a state of the tree
which has the commit already), git handles the merge of the
already-applied patch with grace even if they don't have the same SHA-1.
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2014-05-13 23:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 13:25 Takashi Iwai
2014-05-13 23:23 ` NeilBrown
2014-05-13 23:29 ` Jiri Kosina [this message]
2014-05-13 23:49 ` NeilBrown
2014-05-14 1:40 ` Li Zefan
2014-05-16 3:07 ` Jason Cooper
2014-05-16 5:12 ` Christian Couder
2014-05-16 9:24 ` Li Zefan
2014-05-16 9:33 ` Takashi Iwai
2014-05-18 19:23 ` Christian Couder
2014-05-18 22:12 ` Jason Cooper
2014-05-19 6:34 ` Christian Couder
2014-05-19 13:29 ` Takashi Iwai
2014-05-20 6:37 ` Christian Couder
2014-05-20 7:06 ` Takashi Iwai
2014-05-21 5:36 ` Christian Couder
2014-05-22 4:49 ` Christian Couder
2014-05-22 5:58 ` Takashi Iwai
2014-05-22 6:28 ` Johan Herland
2014-05-22 6:52 ` Christian Couder
2014-05-22 7:29 ` Johan Herland
2014-05-22 7:45 ` Takashi Iwai
2014-05-22 7:49 ` Geert Uytterhoeven
2014-05-22 8:03 ` Takashi Iwai
2014-05-22 15:51 ` Theodore Ts'o
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=alpine.LNX.2.00.1405140127240.16459@pobox.suse.cz \
--to=jkosina@suse.cz \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=neilb@suse.de \
/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