From: Adam Borowski <kilobyte@angband.pl>
To: git@vger.kernel.org
Subject: git-bisect working only from toplevel dir
Date: Wed, 23 Nov 2011 15:50:34 +0100 [thread overview]
Message-ID: <20111123145034.GB17927@angband.pl> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 487 bytes --]
Hi!
The requirement to be in the toplevel directory when calling git-bisect is
pretty infuriating. I tried to find an explanation for this, and the only
reference I found was:
http://thread.gmane.org/gmane.comp.version-control.git/27524/focus=27596
However, since then, git-reset has been changed (in a81c311f). What about
changing git-bisect as well?
A trivial patch seems to work for me, but I might have missed some corner
case.
--
1KB // Yo momma uses IPv4!
[-- Attachment #1.2: 0001-git-bisect-allow-using-it-from-a-subdirectory.patch --]
[-- Type: text/x-diff, Size: 740 bytes --]
From 1dd5dda6a9db3d987e15784c4de24e593cc596e0 Mon Sep 17 00:00:00 2001
From: Adam Borowski <kilobyte@angband.pl>
Date: Wed, 23 Nov 2011 15:08:42 +0100
Subject: [PATCH] git-bisect: allow using it from a subdirectory.
Just like git-reset, restricting it to toplevel is an annoyance, and the
latter has been changed in a81c311f.
---
git-bisect.sh | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/git-bisect.sh b/git-bisect.sh
index 99efbe8..fd6ccdd 100755
--- a/git-bisect.sh
+++ b/git-bisect.sh
@@ -27,6 +27,7 @@ git bisect run <cmd>...
Please use "git help bisect" to get the full man page.'
OPTIONS_SPEC=
+SUBDIRECTORY_OK=Yes
. git-sh-setup
. git-sh-i18n
--
1.7.8.rc3.31.g017d1
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2011-11-23 15:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 14:50 Adam Borowski [this message]
2011-11-23 19:09 ` git-bisect working only from toplevel dir Junio C Hamano
2011-11-23 19:23 ` Jeff King
2011-11-23 20:09 ` Adam Borowski
2011-11-23 21:45 ` Jeff King
2011-11-23 20:26 ` Peter Baumann
2011-11-23 21:36 ` Jeff King
2011-11-23 20:45 ` Junio C Hamano
2011-11-24 7:06 ` Peter Baumann
2011-11-24 11:50 ` Junio C Hamano
2011-11-29 12:06 ` Jeff King
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=20111123145034.GB17927@angband.pl \
--to=kilobyte@angband.pl \
--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).