From: Junio C Hamano
Date: Wed, 14 Mar 2007 11:19:26 +0000 (+0000)
Subject: Autogenerated HTML docs for v1.5.0.3-438-gc49b2
X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=103ad7fa163b20b6629d6162e5b261a124e1e486;p=git.git
Autogenerated HTML docs for v1.5.0.3-438-gc49b2
---
diff --git a/cmds-ancillarymanipulators.txt b/cmds-ancillarymanipulators.txt
index 56d388ef7..28d44fa99 100644
--- a/cmds-ancillarymanipulators.txt
+++ b/cmds-ancillarymanipulators.txt
@@ -7,6 +7,9 @@ gitlink:git-fast-import[1]::
gitlink:git-lost-found[1]::
Recover lost refs that luckily have not yet been pruned.
+gitlink:git-mergetool[1]::
+ Run merge conflict resolution tools to resolve merge conflicts.
+
gitlink:git-pack-refs[1]::
Pack heads and tags for efficient repository access.
diff --git a/config.txt b/config.txt
index 5408dd67d..aaae9ac30 100644
--- a/config.txt
+++ b/config.txt
@@ -453,6 +453,11 @@ merge.summary::
Whether to include summaries of merged commits in newly created
merge commit messages. False by default.
+merge.tool::
+ Controls which merge resolution program is used by
+ gitlink:git-mergetool[l]. Valid values are: "kdiff3", "tkdiff",
+ "meld", "xxdiff", "emerge"
+
merge.verbosity::
Controls the amount of output shown by the recursive merge
strategy. Level 0 outputs nothing except a final error
diff --git a/git-branch.html b/git-branch.html
index 937b288d1..bd07c6531 100644
--- a/git-branch.html
+++ b/git-branch.html
@@ -275,7 +275,7 @@ git-branch(1) Manual Page
git-branch [--color | --no-color] [-r | -a]
[-v [--abbrev=<length> | --no-abbrev]]
-git-branch [-l] [-f] <branchname> [<start-point>]
+git-branch [--track | --no-track] [-l] [-f] <branchname> [<start-point>]
git-branch (-m | -M) [<oldbranch>] <newbranch>
git-branch (-d | -D) [-r] <branchname>…
@@ -289,6 +289,12 @@ and option -a shows both.
It will start out with a head equal to the one given as <start-point>.
If no <start-point> is given, the branch will be created with a head
equal to that of the currently checked out branch.
+When a local branch is started off a remote branch, git can setup the
+branch so that git-pull(1) will appropriately merge from that
+remote branch. If this behavior is desired, it is possible to make it
+the default using the global branch.autosetupmerge configuration
+flag. Otherwise, it can be chosen per-branch using the --track
+and --no-track options.
With a -m or -M option, <oldbranch> will be renamed to <newbranch>.
If <oldbranch> had a corresponding reflog, it is renamed to match
<newbranch>, and a reflog entry is created to remember the branch
@@ -520,7 +526,7 @@ a branch and check it out with a single command.