git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Couder <chriscool@tuxfamily.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: [PATCH] Documentation: add man page for "git bisect--helper"
Date: Tue, 14 Apr 2009 00:00:29 +0200	[thread overview]
Message-ID: <20090414000029.f7b4e880.chriscool@tuxfamily.org> (raw)

Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
---
 Documentation/git-bisect--helper.txt |   41 ++++++++++++++++++++++++++++++++++
 1 files changed, 41 insertions(+), 0 deletions(-)
 create mode 100644 Documentation/git-bisect--helper.txt

diff --git a/Documentation/git-bisect--helper.txt b/Documentation/git-bisect--helper.txt
new file mode 100644
index 0000000..c6ae3f5
--- /dev/null
+++ b/Documentation/git-bisect--helper.txt
@@ -0,0 +1,41 @@
+git-bisect--helper(1)
+=====================
+
+NAME
+----
+git-bisect--helper - helper command for git bisect
+
+SYNOPSIS
+--------
+'git bisect--helper' --next-vars
+
+DESCRIPTION
+-----------
+
+This plumbing command implements some 'git bisect' related
+functionality in C code.
+
+It was created to make it easier to move bisect functionality from the
+"git-bisect.sh" shell script to compiled C code.
+
+OPTIONS
+-------
+--next-vars::
+	Read bisect related references in 'refs/bisect' and use them
+	to compute next bisection point information. Then output this
+	information so that it can easily and safely be eval'ed by a
+	shell script.
+
+Author
+------
+Written by Christian Couder <chriscool@tuxfamily.org> and the git-list
+<git@vger.kernel.org>.
+
+Documentation
+-------------
+Documentation by Christian Couder <chriscool@tuxfamily.org> and the
+git-list <git@vger.kernel.org>.
+
+GIT
+---
+Part of the linkgit:git[1] suite
-- 
1.6.2.2.572.g4420a

                 reply	other threads:[~2009-04-13 22:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20090414000029.f7b4e880.chriscool@tuxfamily.org \
    --to=chriscool@tuxfamily.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).