Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(277)

Unified Diff: docs/src/git-new-branch.txt

Issue 259863004: Move docs folder to man. (Closed) Base URL: https://chromium.googlesource.com/chromium/tools/depot_tools.git@master
Patch Set: Created 6 years, 8 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « docs/src/git-nav-upstream.demo.1.sh ('k') | docs/src/git-new-branch.demo.1.sh » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: docs/src/git-new-branch.txt
diff --git a/docs/src/git-new-branch.txt b/docs/src/git-new-branch.txt
deleted file mode 100644
index a9f104f399171d23fc55b10fc581beadd73fce2d..0000000000000000000000000000000000000000
--- a/docs/src/git-new-branch.txt
+++ /dev/null
@@ -1,81 +0,0 @@
-git-new-branch(1)
-=================
-
-NAME
-----
-git-new-branch -
-include::_git-new-branch_desc.helper.txt[]
-
-SYNOPSIS
---------
-[verse]
-'git new-branch' <branch_name>
-'git new-branch' --upstream_current <branch_name>
-'git new-branch' --upstream <REF> <branch_name>
-'git new-branch' --lkgr <branch_name>
-
-DESCRIPTION
------------
-
-Creates a new branch. By default the new branch will track the configured
-upstream for the repo (defaults to 'origin/master'). If one of the other options
-is specified, it will track that other ref instead.
-
-Conceptually, each branch in your repo represents one 'Change List (CL)'. If you
-have many independent CLs (i.e. the changes in one do not interact with/depend
-on the changes in another), then you should create them as new branches tracking
-the default upstream (i.e. `git new-branch <branch_name>`). If you have features
-which depend on each other, you should create stacked branches using `git
-new-branch --upstream_current <branch_name>`.
-
-OPTIONS
--------
-
---upstream_current::
- Set the tracking (upstream) branch to the currently-checked-out branch.
-
---uptstream <REF>::
- Set the tracking (upstream) branch to <REF>. <REF> may be a local branch,
- remote branch, or a tag.
-
---lkgr::
- Alias for `--upstream lkgr`.
-
-<branch_name>::
- The name for the new branch.
-
-
-CONFIGURATION VARIABLES
------------------------
-
-depot-tools.upstream
-~~~~~~~~~~~~~~~~~~~~
-
-This configures the default 'upstream' for all new branches. If it is unset, it
-defaults to 'origin/master'. This is considered to be the 'root' branch.
-
-EXAMPLE
--------
-demo:1[]
-
-1. Note that both branches are cyan because they are currently the same
-'commit' object. See linkgit:git-map-branches[1] for more detail.
-
-include::_aliases.txt[]
-
-----
-[alias]
- git nb = new-branch
- git tb = new-branch --upstream_current <1>
-----
-<1> mnemonic: tb -> "track branch"
-
-
-SEE ALSO
---------
-linkgit:git-rebase-update[1], linkgit:git-reparent-branch[1],
-linkgit:git-rename-branch[1], linkgit:git-upstream-diff[1]
-
-include::_footer.txt[]
-
-// vim: ft=asciidoc:
« no previous file with comments | « docs/src/git-nav-upstream.demo.1.sh ('k') | docs/src/git-new-branch.demo.1.sh » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698