From e79159d5498ad2b14be1b372eab269a78cfc3443 Mon Sep 17 00:00:00 2001 From: Junio C Hamano Date: Sat, 12 Apr 2008 08:23:17 +0000 Subject: [PATCH] Autogenerated HTML docs for v1.5.5-40-g4cdda --- git-bisect.html | 8 ++++++-- git-bisect.txt | 7 +++++++ git-commit.html | 18 +++++++++++++++++- git-commit.txt | 11 +++++++++++ git-request-pull.html | 4 ++-- git-request-pull.txt | 2 +- git-tag.html | 6 +++--- git-tag.txt | 4 ++-- 8 files changed, 49 insertions(+), 11 deletions(-) diff --git a/git-bisect.html b/git-bisect.html index 5df54707e..438979162 100644 --- a/git-bisect.html +++ b/git-bisect.html @@ -280,7 +280,8 @@ git-bisect(1) Manual Page on the subcommand:

-
git bisect start [<bad> [<good>...]] [--] [<paths>...]
+
git bisect help
+git bisect start [<bad> [<good>...]] [--] [<paths>...]
 git bisect bad [<rev>]
 git bisect good [<rev>...]
 git bisect skip [<rev>...]
@@ -293,6 +294,9 @@ git bisect run <cmd>...

 
This command uses git-rev-list --bisect option to help drive the
 binary search process to find which change introduced a bug, given an
 old "good" commit object name and a later "bad" commit object name.

+
Getting help

+
Use "git bisect" to get a short usage description, and "git bisect
+help" or "git bisect -h" to get a long usage description.

 
Basic bisect commands: start, bad, good

 
The way you use it is:

 

@@ -453,7 +457,7 @@ know the outcome.

 

 
 
diff --git a/git-bisect.txt b/git-bisect.txt
index 96585ae8d..698ffde7c 100644
--- a/git-bisect.txt
+++ b/git-bisect.txt
@@ -15,6 +15,7 @@ DESCRIPTION
 The command takes various subcommands, and different options depending
 on the subcommand:
 
+ git bisect help
  git bisect start [ [...]] [--] [...]
  git bisect bad []
  git bisect good [...]
@@ -29,6 +30,12 @@ This command uses 'git-rev-list --bisect' option to help drive the
 binary search process to find which change introduced a bug, given an
 old "good" commit object name and a later "bad" commit object name.
 
+Getting help
+~~~~~~~~~~~~
+
+Use "git bisect" to get a short usage description, and "git bisect
+help" or "git bisect -h" to get a long usage description.
+
 Basic bisect commands: start, bad, good
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
diff --git a/git-commit.html b/git-commit.html
index 5e7e4aaf0..0b1c56969 100644
--- a/git-commit.html
+++ b/git-commit.html
@@ -481,6 +481,22 @@ that, you can recover from it with git-reset(1).

 
 

+-o|--only
+

+

+

+        Make a commit only from the paths specified on the
+        command line, disregarding any contents that have been
+        staged so far. This is the default mode of operation of
+        git commit if any paths are given on the command line,
+        in which case this option can be omitted.
+        If this option is specified together with --amend, then
+        no paths need be specified, which can be used to amend
+        the last commit without committing changes that have
+        already been staged.
+

+

+

 -u|--untracked-files
 

 

@@ -730,7 +746,7 @@ Junio C Hamano <junkio@cox.net>
diff --git a/git-commit.txt b/git-commit.txt index b4ae61ff4..4bb51cc06 100644 --- a/git-commit.txt +++ b/git-commit.txt @@ -139,6 +139,17 @@ but can be used to amend a merge commit. as well. This is usually not what you want unless you are concluding a conflicted merge. +-o|--only:: + Make a commit only from the paths specified on the + command line, disregarding any contents that have been + staged so far. This is the default mode of operation of + 'git commit' if any paths are given on the command line, + in which case this option can be omitted. + If this option is specified together with '--amend', then + no paths need be specified, which can be used to amend + the last commit without committing changes that have + already been staged. + -u|--untracked-files:: Show all untracked files, also those in uninteresting directories, in the "Untracked files:" section of commit diff --git a/git-request-pull.html b/git-request-pull.html index f6b71a970..1ad2fe5df 100644 --- a/git-request-pull.html +++ b/git-request-pull.html @@ -303,7 +303,7 @@ the given URL in the generated summary.

- Commit to send at; defaults to HEAD. + Commit to end at; defaults to HEAD.

@@ -322,7 +322,7 @@ the given URL in the generated summary.

diff --git a/git-request-pull.txt b/git-request-pull.txt index 270df9b18..9a14c04e3 100644 --- a/git-request-pull.txt +++ b/git-request-pull.txt @@ -24,7 +24,7 @@ OPTIONS URL to include in the summary. :: - Commit to send at; defaults to HEAD. + Commit to end at; defaults to HEAD. Author ------ diff --git a/git-tag.html b/git-tag.html index 09564a095..77ff1c5a8 100644 --- a/git-tag.html +++ b/git-tag.html @@ -528,13 +528,13 @@ to specify the date to embed inside of the tag object. The data in the tag object affects, for example, the ordering of tags in the gitweb interface.

To set the date used in future tag objects, set the environment -variable GIT_AUTHOR_DATE to one or more of the date and time. The +variable GIT_COMMITTER_DATE to one or more of the date and time. The date and time can be specified in a number of ways; the most common is "YYYY-MM-DD HH:MM".

An example follows.

-
$ GIT_AUTHOR_DATE="2006-10-02 10:31" git tag -s v1.0.1
+
$ GIT_COMMITTER_DATE="2006-10-02 10:31" git tag -s v1.0.1

Author

@@ -552,7 +552,7 @@ Junio C Hamano <junkio@cox.net> and Chris Wright <chrisw@osdl.org>.< diff --git a/git-tag.txt b/git-tag.txt index 4b6fd90ea..9712392f7 100644 --- a/git-tag.txt +++ b/git-tag.txt @@ -233,14 +233,14 @@ the tag object affects, for example, the ordering of tags in the gitweb interface. To set the date used in future tag objects, set the environment -variable GIT_AUTHOR_DATE to one or more of the date and time. The +variable GIT_COMMITTER_DATE to one or more of the date and time. The date and time can be specified in a number of ways; the most common is "YYYY-MM-DD HH:MM". An example follows. ------------ -$ GIT_AUTHOR_DATE="2006-10-02 10:31" git tag -s v1.0.1 +$ GIT_COMMITTER_DATE="2006-10-02 10:31" git tag -s v1.0.1 ------------ -- 2.26.2