From: Jon Seymour <jon.seymour@gmail.com>
To: git@vger.kernel.org
Cc: j6t@kdbg.org, gitster@pobox.com, jnareb@gmail.com,
Jon Seymour <jon.seymour@gmail.com>
Subject: [PATCH 5/5] bisect: add documentation for --no-checkout[=<ref>] option.
Date: Sat, 30 Jul 2011 18:28:31 +1000 [thread overview]
Message-ID: <1312014511-7157-6-git-send-email-jon.seymour@gmail.com> (raw)
In-Reply-To: <1312014511-7157-1-git-send-email-jon.seymour@gmail.com>
Signed-off-by: Jon Seymour <jon.seymour@gmail.com>
---
Documentation/git-bisect.txt | 26 +++++++++++++++++++++++++-
1 files changed, 25 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt
index ab60a18..0ad3b01 100644
--- a/Documentation/git-bisect.txt
+++ b/Documentation/git-bisect.txt
@@ -17,7 +17,7 @@ The command takes various subcommands, and different options depending
on the subcommand:
git bisect help
- git bisect start [<bad> [<good>...]] [--] [<paths>...]
+ git bisect start [--no-checkout[=<ref>]] [<bad> [<good>...]] [--] [<paths>...]
git bisect bad [<rev>]
git bisect good [<rev>...]
git bisect skip [(<rev>|<range>)...]
@@ -263,6 +263,17 @@ rewind the tree to the pristine state. Finally the script should exit
with the status of the real test to let the "git bisect run" command loop
determine the eventual outcome of the bisect session.
+OPTIONS
+-------
+--no-checkout[=<ref>]::
++
+If this option is specified, git bisect does not update the working tree
+or index but instead simply updates the specified reference. <ref> defaults
+to HEAD if not specified.
++
+This option is useful in circumstances in which checkout is either not
+possible (because of a damaged respository) or otherwise not required.
+
EXAMPLES
--------
@@ -343,6 +354,19 @@ $ git bisect run sh -c "make || exit 125; ~/check_test_case.sh"
This shows that you can do without a run script if you write the test
on a single line.
+* Locate the earliest damaged commit in a repository
++
+------------
+$ git bisect start HEAD <known-good-commit> [ <missing-or-damaged-commit> ... ] --no-checkout
+$ git bisect run eval "
+git rev-list --objects HEAD >/dev/null &&
+git rev-list --objects HEAD | git pack-objects --stdout >/dev/null || false"
+------------
++
+This shows how to use `git bisect --no-checkout` with a repository containing damaged commits
+to find the earliest commit reachable from the HEAD commit such that the graph rooted at the
+parents of that commit is undamaged.
+
SEE ALSO
--------
link:git-bisect-lk2009.html[Fighting regressions with git bisect],
--
1.7.6.387.g991c2
next prev parent reply other threads:[~2011-07-30 8:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-30 8:28 [PATCH 0/5] bisect: Add support for a --no-checkout option Jon Seymour
2011-07-30 8:28 ` [PATCH 1/5] bisect: add tests to document expected behaviour in presence of broken trees Jon Seymour
2011-07-30 8:28 ` [PATCH 2/5] bisect: introduce support for --no-checkout=<ref> option Jon Seymour
2011-07-30 13:49 ` Christian Couder
2011-07-30 8:28 ` [PATCH 3/5] bisect: introduce --no-checkout[=<ref>] support into porcelain Jon Seymour
2011-07-30 14:34 ` Christian Couder
2011-07-30 17:00 ` Jon Seymour
2011-07-31 0:36 ` Christian Couder
2011-08-01 0:53 ` Junio C Hamano
2011-08-01 4:35 ` Christian Couder
2011-07-30 8:28 ` [PATCH 4/5] bisect: add tests for the --no-checkout option Jon Seymour
2011-07-30 8:28 ` Jon Seymour [this message]
2011-07-30 8:30 ` [PATCH 0/5] bisect: Add support for a " Jon Seymour
2011-07-30 13:48 ` Christian Couder
2011-07-30 13:58 ` Jon Seymour
2011-07-30 14:19 ` Christian Couder
2011-08-01 1:00 ` Junio C Hamano
2011-08-01 4:42 ` Christian Couder
2011-08-01 5:27 ` Jon Seymour
2011-08-01 17:33 ` Junio C Hamano
2011-08-01 22:19 ` Jon Seymour
2011-08-01 23:33 ` Junio C Hamano
2011-08-02 1:15 ` Jon Seymour
2011-08-02 1:41 ` Jon Seymour
2011-08-02 17:53 ` Junio C Hamano
2011-08-02 21:27 ` Jon Seymour
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=1312014511-7157-6-git-send-email-jon.seymour@gmail.com \
--to=jon.seymour@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=jnareb@gmail.com \
/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).