From: Adam Dinwoodie <adam@dinwoodie.org>
To: git@vger.kernel.org
Subject: [RFC PATCH] rebisect: add script for easier bisect log editing
Date: Wed, 8 Nov 2017 13:59:31 +0000 [thread overview]
Message-ID: <20171108135931.166880-1-adam@dinwoodie.org> (raw)
Add a short script, vaguely inspired by `git rebase --interactive`, to
ease the process described in the `git bisect` documentation of saving
off a bisect log, editing it, then replaying it.
Signed-off-by: Adam Dinwoodie <adam@dinwoodie.org>
---
When I'm bisecting, I find I need to semi-regularly go back and change
my good/bad/skip response for some commits. The bisect documentation
describes doing this by saving `git bisect log` output, editing it, then
using `git bisect replay`. Which is a perfectly fine technique, but
automation is A Good Thing(TM). The below script is a short proof of
concept for changing this process to be a single command.
Ideally (at least from my perspective), this function would be rolled
into the main `git bisect` tool, as `git bisect edit` or similar.
Before I start working on that, however, I wanted to see what the list
thought of the idea.
contrib/git-rebisect.sh | 12 ++++++++++++
1 file changed, 12 insertions(+)
create mode 100755 contrib/git-rebisect.sh
diff --git a/contrib/git-rebisect.sh b/contrib/git-rebisect.sh
new file mode 100755
index 000000000..60f20b278
--- /dev/null
+++ b/contrib/git-rebisect.sh
@@ -0,0 +1,12 @@
+#!/bin/sh
+
+GIT_EDITOR="$(git var GIT_EDITOR)"
+GIT_DIR="$(git rev-parse --git-dir)"
+GIT_BISECT_LOG_TMP="${GIT_DIR}/BISECT_LOG_EDIT"
+
+git bisect log >"$GIT_BISECT_LOG_TMP"
+"$GIT_EDITOR" "$GIT_BISECT_LOG_TMP"
+git bisect reset HEAD
+git bisect start
+git bisect replay "$GIT_BISECT_LOG_TMP"
+rm -f "$GIT_BISECT_LOG_TMP"
--
2.14.3
next reply other threads:[~2017-11-08 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 13:59 Adam Dinwoodie [this message]
2017-11-08 16:12 ` [RFC PATCH] rebisect: add script for easier bisect log editing Christian Couder
2017-11-08 16:15 ` Christian Couder
2017-11-08 16:50 ` Adam Dinwoodie
2017-11-08 16:32 ` Adam Dinwoodie
2017-11-20 18:24 ` [RFC PATCH v2 0/2] bisect: add a single command for editing logs Adam Dinwoodie
2017-11-22 5:35 ` Junio C Hamano
2017-11-20 18:24 ` [RFC PATCH v2 1/2] bisect: split out replay file parsing Adam Dinwoodie
2017-11-20 18:24 ` [RFC PATCH v2 2/2] bisect: add "edit" command Adam Dinwoodie
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171108135931.166880-1-adam@dinwoodie.org \
--to=adam@dinwoodie.org \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).