An optional parameter needs to be typeset with unconstrained pairs - [<repository>]+ [<repository>]
Placeholders are spelled in lowercase and enclosed in angle brackets surrounded by underscores: _<file>_ - _<commit>_+ _<commit>_
An optional parameter needs to be typeset with unconstrained pairs - [<repository>]+ [<repository>]
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a|-d|<branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a|-d|<branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
Placeholders are spelled in lowercase and enclosed in angle brackets surrounded by underscores: _<file>_ - _<commit>_+ _<commit>_
[(`-p` _<parent>_)...] -(Any number of option -p, each with one <parent> argument.)+
[(`-p` _<parent>_)...] +(Any number of option -p, each with one <parent> argument.)
`git remote set-head` _<name>_ (`-a` | `-d` | _<branch>_) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +`git remote set-head` _<name>_ (`-a` | `-d` | _<branch>_) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
Placeholders are spelled in lowercase and enclosed in angle brackets surrounded by underscores: _<file>_ - _<commit>_+ _<commit>_
[(`-p` _<parent>_)...] -(Any number of option -p, each with one <parent> argument.)+
[(`-p` _<parent>_)...] +(Any number of option -p, each with one <parent> argument.)
`git remote set-head` _<name>_ (`-a` | `-d` | _<branch>_) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +`git remote set-head` _<name>_ (`-a` | `-d` | _<branch>_) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
Placeholders are spelled in lowercase and enclosed in angle brackets surrounded by underscores: _<file>_ - _<commit>_+ _<commit>_
[(`-p` _<parent>_)...] -(Any number of option -p, each with one <parent> argument.)+
[(`-p` _<parent>_)...] +(Any number of option -p, each with one <parent> argument.)
`git remote set-head` _<name>_ (`-a` | `-d` | _<branch>_) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +`git remote set-head` _<name>_ (`-a` | `-d` | _<branch>_) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
Placeholders are spelled in lowercase and enclosed in angle brackets surrounded by underscores: _<file>_ - _<commit>_+ _<commit>_
An optional parameter needs to be typeset with unconstrained pairs - [<repository>]+ [<repository>]
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a|-d|<branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a|-d|<branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
Placeholders are spelled in lowercase and enclosed in angle brackets surrounded by underscores: _<file>_ - _<commit>_+ _<commit>_
An optional parameter needs to be typeset with unconstrained pairs - [<repository>]+ [<repository>]
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a|-d|<branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a|-d|<branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
Placeholders are spelled in lowercase and enclosed in angle brackets surrounded by underscores: _<file>_ - _<commit>_+ _<commit>_
An optional parameter needs to be typeset with unconstrained pairs - [<repository>]+ [<repository>]
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a|-d|<branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a|-d|<branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
Placeholders are spelled in lowercase and enclosed in angle brackets surrounded by underscores: _<file>_ - _<commit>_+ _<commit>_
An optional parameter needs to be typeset with unconstrained pairs - [<repository>]+ [<repository>]
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a|-d|<branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a|-d|<branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
[(-p <parent>)...] -(Any number of option -p, each with one <parent> argument.)+
[(-p <parent>)...] +(Any number of option -p, each with one <parent> argument.)
git remote set-head <name> (-a | -d | <branch>) -(One and only one of "-a", "-d" or "<branch>" _must_ (no square +git remote set-head <name> (-a | -d | <branch>) +(One and only one of "-a", "-d" or "<branch>" _must_ (no square brackets) be provided.)
git show -s --pretty=reference <commit>+
git show -s --pretty=reference <commit>
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>+
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>
git show -s --date=short --pretty='format:%h ("%s", %ad)' <commit>
+git show -s --date=short --pretty='format:%h ("%s", %ad)' <commit>
git show -s --date=short --pretty='format:%h ("%s", %ad)' <commit>
+ git show -s --date=short --pretty='format:%h ("%s", %ad)' <commit>
git show -s --date=short --pretty='format:%h ("%s", %ad)' <commit>
+ git show -s --date=short --pretty='format:%h ("%s", %ad)' <commit>
git show -s --date=short --pretty='format:%h ("%s", %ad)' <commit>
+ git show -s --date=short --pretty='format:%h ("%s", %ad)' <commit>
git show -s --date=short --pretty='format:%h ("%s", %ad)' <commit>
+ git show -s --date=short --pretty='format:%h ("%s", %ad)' <commit>
git show -s --date=short --pretty='format:%h ("%s", %ad)' <commit>
+ git show -s --date=short --pretty='format:%h ("%s", %ad)' <commit>
git show -s --date=short --pretty='format:%h ("%s", %ad)' <commit>
+ git show -s --date=short --pretty='format:%h ("%s", %ad)' <commit>
git show -s --date=short --pretty='format:%h ("%s", %ad)' <commit>
+ git show -s --date=short --pretty='format:%h ("%s", %ad)' <commit>
git show -s --pretty=reference <commit>+
git show -s --pretty=reference <commit>
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>+
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>
git show -s --pretty=reference <commit>+
git show -s --pretty=reference <commit>
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>+
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>
git show -s --pretty=reference <commit>+
git show -s --pretty=reference <commit>
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>+
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>
git show -s --pretty=reference <commit>+
git show -s --pretty=reference <commit>
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>+
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>
git show -s --pretty=reference <commit>+
git show -s --pretty=reference <commit>
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>+
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>
git show -s --pretty=reference <commit>+
git show -s --pretty=reference <commit>
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>+
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>
git show -s --pretty=reference <commit>+
git show -s --pretty=reference <commit>
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>+
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>
git show -s --pretty=reference <commit>+
git show -s --pretty=reference <commit>
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>+
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>
git show -s --pretty=reference <commit>+
git show -s --pretty=reference <commit>
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>+
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>
git show -s --pretty=reference <commit>+
git show -s --pretty=reference <commit>
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>+
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>
git show -s --pretty=reference <commit>+
git show -s --pretty=reference <commit>
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>+
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>
git show -s --pretty=reference <commit>+
git show -s --pretty=reference <commit>
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>+
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>
git show -s --pretty=reference <commit>+
git show -s --pretty=reference <commit>
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>+
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>
git show -s --pretty=reference <commit>+
git show -s --pretty=reference <commit>
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>+
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>
git show -s --pretty=reference <commit>+
git show -s --pretty=reference <commit>
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>+
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>
git show -s --pretty=reference <commit>+
git show -s --pretty=reference <commit>
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>+
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>
git show -s --pretty=reference <commit>+
git show -s --pretty=reference <commit>
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>+
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>
git show -s --pretty=reference <commit>+
git show -s --pretty=reference <commit>
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>+
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>
git show -s --pretty=reference <commit>+
git show -s --pretty=reference <commit>
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>+
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>
git show -s --pretty=reference <commit>+
git show -s --pretty=reference <commit>
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>+
git show -s --date=short --pretty='format:%h (%s, %ad)' <commit>
arg_str is the string that is shown as argument
-(e.g. "branch" will result in <branch>).
+(e.g. "branch" will result in <branch>).
If set to NULL, three dots (...) will be displayed.
arg_str is the string that is shown as argument
-(e.g. "branch" will result in <branch>).
+(e.g. "branch" will result in <branch>).
If set to NULL, three dots (...) will be displayed.
arg_str is the string that is shown as argument
-(e.g. "branch" will result in <branch>).
+(e.g. "branch" will result in <branch>).
If set to NULL, three dots (...) will be displayed.
arg_str is the string that is shown as argument
-(e.g. "branch" will result in <branch>).
+(e.g. "branch" will result in <branch>).
If set to NULL, three dots (...) will be displayed.
arg_str is the string that is shown as argument
-(e.g. "branch" will result in <branch>).
+(e.g. "branch" will result in <branch>).
If set to NULL, three dots (...) will be displayed.
arg_str is the string that is shown as argument
-(e.g. "branch" will result in <branch>).
+(e.g. "branch" will result in <branch>).
If set to NULL, three dots (...) will be displayed.
arg_str is the string that is shown as argument
-(e.g. "branch" will result in <branch>).
+(e.g. "branch" will result in <branch>).
If set to NULL, three dots (...) will be displayed.
arg_str is the string that is shown as argument
-(e.g. "branch" will result in <branch>).
+(e.g. "branch" will result in <branch>).
If set to NULL, three dots (...) will be displayed.
arg_str is the string that is shown as argument
-(e.g. "branch" will result in <branch>).
+(e.g. "branch" will result in <branch>).
If set to NULL, three dots (...) will be displayed.
arg_str is the string that is shown as argument
-(e.g. "branch" will result in <branch>).
+(e.g. "branch" will result in <branch>).
If set to NULL, three dots (...) will be displayed.
arg_str is the string that is shown as argument
-(e.g. "branch" will result in <branch>).
+(e.g. "branch" will result in <branch>).
If set to NULL, three dots (...) will be displayed.
arg_str is the string that is shown as argument
-(e.g. "branch" will result in <branch>).
+(e.g. "branch" will result in <branch>).
If set to NULL, three dots (...) will be displayed.
arg_str is the string that is shown as argument
-(e.g. "branch" will result in <branch>).
+(e.g. "branch" will result in <branch>).
If set to NULL, three dots (...) will be displayed.
git-diff-index <tree-ish> git-diff-index <tree-ish> compares the <tree-ish> and the files on the filesystem.
+compares the <tree-ish> and the files on the filesystem.
git-diff-index --cached <tree-ish> git-diff-index --cached <tree-ish> compares the <tree-ish> and the index.
+compares the <tree-ish> and the index.
git-diff-tree [-r] <tree-ish-1> <tree-ish-2> [<pattern>...] ..<hash> <mode>
File modes <mode> are printed as 6-digit octal numbers including the file type @@ -416,7 +416,7 @@
It is followed by one or more extended header lines (this example shows a merge with two parents):
index<hash>,<hash>..<hash> +@@ -426,7 +426,7 @@index<hash>,<hash>..<hash>mode<mode>,<mode>..<mode>newfilemode<mode>deletedfilemode<mode>,<mode>< the <mode> is different from the rest. Extended headers with information about detected content movement (renames and copying detection) are designed to work with the diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
compares the <tree-ish> and the files on the filesystem.
+compares the <tree-ish> and the files on the filesystem.
compares the <tree-ish> and the index.
+compares the <tree-ish> and the index.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -401,7 +401,7 @@< the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
compares the <tree-ish> and the files on the filesystem.
+compares the <tree-ish> and the files on the filesystem.
compares the <tree-ish> and the index.
+compares the <tree-ish> and the index.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -423,7 +423,7 @@< the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
compares the <tree-ish> and the files on the filesystem.
+compares the <tree-ish> and the files on the filesystem.
compares the <tree-ish> and the index.
+compares the <tree-ish> and the index.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -410,7 +410,7 @@< the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
compares the <tree-ish> and the files on the filesystem.
+compares the <tree-ish> and the files on the filesystem.
compares the <tree-ish> and the index.
+compares the <tree-ish> and the index.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -428,7 +428,7 @@< the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
compares the <tree-ish> and the files on the filesystem.
+compares the <tree-ish> and the files on the filesystem.
compares the <tree-ish> and the index.
+compares the <tree-ish> and the index.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -426,7 +426,7 @@< the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
compares the <tree-ish> and the files on the filesystem.
+compares the <tree-ish> and the files on the filesystem.
compares the <tree-ish> and the index.
+compares the <tree-ish> and the index.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -435,7 +435,7 @@< the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
compares the <tree-ish> and the files on the filesystem.
+compares the <tree-ish> and the files on the filesystem.
compares the <tree-ish> and the index.
+compares the <tree-ish> and the index.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -436,7 +436,7 @@< the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
compares the <tree-ish> and the files on the filesystem.
+compares the <tree-ish> and the files on the filesystem.
compares the <tree-ish> and the index.
+compares the <tree-ish> and the index.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -400,7 +400,7 @@< the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
compares the <tree-ish> and the files on the filesystem.
+compares the <tree-ish> and the files on the filesystem.
compares the <tree-ish> and the index.
+compares the <tree-ish> and the index.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -431,7 +431,7 @@< the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
compares the <tree-ish> and the files on the filesystem.
+compares the <tree-ish> and the files on the filesystem.
compares the <tree-ish> and the index.
+compares the <tree-ish> and the index.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -445,7 +445,7 @@< the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
compares the <tree-ish> and the files on the filesystem.
+compares the <tree-ish> and the files on the filesystem.
compares the <tree-ish> and the index.
+compares the <tree-ish> and the index.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -455,7 +455,7 @@< the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
compares the <tree-ish> and the files on the filesystem.
+compares the <tree-ish> and the files on the filesystem.
compares the <tree-ish> and the index.
+compares the <tree-ish> and the index.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -446,7 +446,7 @@< the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
compares the <tree-ish> and the files on the filesystem.
+compares the <tree-ish> and the files on the filesystem.
compares the <tree-ish> and the index.
+compares the <tree-ish> and the index.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -404,7 +404,7 @@< the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
compares the <tree-ish> and the files on the filesystem.
+compares the <tree-ish> and the files on the filesystem.
compares the <tree-ish> and the index.
+compares the <tree-ish> and the index.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -442,7 +442,7 @@< the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
compares the <tree-ish> and the files on the filesystem.
+compares the <tree-ish> and the files on the filesystem.
compares the <tree-ish> and the index.
+compares the <tree-ish> and the index.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -455,7 +455,7 @@< the <mode> is different from the rest. Extended headers with information about detected content movement (renames and copying detection) are designed to work with the diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
git-diff-index <tree-ish> git-diff-index <tree-ish> compares the <tree-ish> and the files on the filesystem.
+compares the <tree-ish> and the files on the filesystem.
git-diff-index --cached <tree-ish> git-diff-index --cached <tree-ish> compares the <tree-ish> and the index.
+compares the <tree-ish> and the index.
git-diff-tree [-r] <tree-ish-1> <tree-ish-2> [<pattern>...] ..<hash> <mode>
File modes <mode> are printed as 6-digit octal numbers including the file type @@ -421,7 +421,7 @@
It is followed by one or more extended header lines (this example shows a merge with two parents):
index<hash>,<hash>..<hash> +@@ -431,7 +431,7 @@index<hash>,<hash>..<hash>mode<mode>,<mode>..<mode>newfilemode<mode>deletedfilemode<mode>,<mode>< the <mode> is different from the rest. Extended headers with information about detected content movement (renames and copying detection) are designed to work with the diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
git-diff-index <tree-ish> git-diff-index <tree-ish> compares the <tree-ish> and the files on the filesystem.
+compares the <tree-ish> and the files on the filesystem.
git-diff-index --cached <tree-ish> git-diff-index --cached <tree-ish> compares the <tree-ish> and the index.
+compares the <tree-ish> and the index.
git-diff-tree [-r] <tree-ish-1> <tree-ish-2> [<pattern>...] ..<hash> <mode>
File modes <mode> are printed as 6-digit octal numbers including the file type @@ -415,7 +415,7 @@
It is followed by one or more extended header lines (this example shows a merge with two parents):
index<hash>,<hash>..<hash> +@@ -425,7 +425,7 @@index<hash>,<hash>..<hash>mode<mode>,<mode>..<mode>newfilemode<mode>deletedfilemode<mode>,<mode>< the <mode> is different from the rest. Extended headers with information about detected content movement (renames and copying detection) are designed to work with the diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
compares the <tree-ish> and the files on the filesystem.
+compares the <tree-ish> and the files on the filesystem.
compares the <tree-ish> and the index.
+compares the <tree-ish> and the index.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -403,7 +403,7 @@< the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
..<hash> <mode>
File modes <mode> are printed as 6-digit octal numbers including the file type @@ -191,7 +191,7 @@
It is followed by one or more extended header lines (this example shows a merge with two parents):
index<hash>,<hash>..<hash> +@@ -201,7 +201,7 @@index<hash>,<hash>..<hash>mode<mode>,<mode>..<mode>newfilemode<mode>deletedfilemode<mode>,<mode>< the <mode> is different from the rest. Extended headers with information about detected content movement (renames and copying detection) are designed to work with the diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -197,7 +197,7 @@< the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -227,7 +227,7 @@< the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -203,7 +203,7 @@< the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -215,7 +215,7 @@< the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -211,7 +211,7 @@< the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -206,7 +206,7 @@< the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -265,7 +265,7 @@< the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -198,7 +198,7 @@< the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -217,7 +217,7 @@< the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -230,7 +230,7 @@< the <mode> is different from the rest. Extended headers with information about detected content movement (renames and copying detection) are designed to work with the diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
..<hash> <mode>
File modes <mode> are printed as 6-digit octal numbers including the file type @@ -196,7 +196,7 @@
It is followed by one or more extended header lines (this example shows a merge with two parents):
index<hash>,<hash>..<hash> +@@ -206,7 +206,7 @@index<hash>,<hash>..<hash>mode<mode>,<mode>..<mode>newfilemode<mode>deletedfilemode<mode>,<mode>< the <mode> is different from the rest. Extended headers with information about detected content movement (renames and copying detection) are designed to work with the diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
..<hash> <mode>
File modes <mode> are printed as 6-digit octal numbers including the file type @@ -190,7 +190,7 @@
It is followed by one or more extended header lines (this example shows a merge with two parents):
index<hash>,<hash>..<hash> +@@ -200,7 +200,7 @@index<hash>,<hash>..<hash>mode<mode>,<mode>..<mode>newfilemode<mode>deletedfilemode<mode>,<mode>< the <mode> is different from the rest. Extended headers with information about detected content movement (renames and copying detection) are designed to work with the diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
index <hash>,<hash>..<hash> +index <hash>,<hash>..<hash> mode <mode>,<mode>..<mode> new file mode <mode> deleted file mode <mode>,<mode>@@ -197,7 +197,7 @@< the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two -<tree-ish> and are not used by combined diff format. +<tree-ish> and are not used by combined diff format.
Deepen or shorten the history of a shallow repository to include all reachable commits after <date>.
-Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. @@ -136,7 +136,7 @@
When git fetch is used with <src>:<dst> refspec, it may
refuse to update the local branch as discussed
-in the <refspec> part below.
+in the <refspec> part below.
This option overrides that check.
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the
specified refspec (can be given more than once) to map the
refs to remote-tracking branches, instead of the values of
remote.*.fetch configuration variables for the remote
-repository. Providing an empty <refspec> to the
+repository. Providing an empty <refspec> to the
--refmap option causes Git to ignore the configured
refspecs and rely entirely on the refspecs supplied as
command-line arguments. See section on "Configured Remote-tracking
diff --git a/external/docs/content/docs/fetch-options/2.0.5.html b/external/docs/content/docs/fetch-options/2.0.5.html
index 3199b93ecf..13245a3c3b 100644
--- a/external/docs/content/docs/fetch-options/2.0.5.html
+++ b/external/docs/content/docs/fetch-options/2.0.5.html
@@ -69,8 +69,8 @@
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the specified refspec (can be given more than once) to map the diff --git a/external/docs/content/docs/fetch-options/2.11.4.html b/external/docs/content/docs/fetch-options/2.11.4.html index e32776efb2..858b526a97 100644 --- a/external/docs/content/docs/fetch-options/2.11.4.html +++ b/external/docs/content/docs/fetch-options/2.11.4.html @@ -49,7 +49,7 @@
Deepen or shorten the history of a shallow repository to include all reachable commits after <date>.
Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. @@ -92,8 +92,8 @@
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the specified refspec (can be given more than once) to map the diff --git a/external/docs/content/docs/fetch-options/2.17.0.html b/external/docs/content/docs/fetch-options/2.17.0.html index de6d28047c..44b5f78dde 100644 --- a/external/docs/content/docs/fetch-options/2.17.0.html +++ b/external/docs/content/docs/fetch-options/2.17.0.html @@ -50,7 +50,7 @@
Deepen or shorten the history of a shallow repository to include all reachable commits after <date>.
Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. @@ -93,8 +93,8 @@
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the specified refspec (can be given more than once) to map the diff --git a/external/docs/content/docs/fetch-options/2.18.0.html b/external/docs/content/docs/fetch-options/2.18.0.html index cbff7531a2..7a2b5f78f5 100644 --- a/external/docs/content/docs/fetch-options/2.18.0.html +++ b/external/docs/content/docs/fetch-options/2.18.0.html @@ -49,7 +49,7 @@
Deepen or shorten the history of a shallow repository to include all reachable commits after <date>.
Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. @@ -92,8 +92,8 @@
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the specified refspec (can be given more than once) to map the diff --git a/external/docs/content/docs/fetch-options/2.19.0.html b/external/docs/content/docs/fetch-options/2.19.0.html index ed544b3e51..cedb95ff36 100644 --- a/external/docs/content/docs/fetch-options/2.19.0.html +++ b/external/docs/content/docs/fetch-options/2.19.0.html @@ -50,7 +50,7 @@
Deepen or shorten the history of a shallow repository to include all reachable commits after <date>.
Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. @@ -116,8 +116,8 @@
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the specified refspec (can be given more than once) to map the diff --git a/external/docs/content/docs/fetch-options/2.20.0.html b/external/docs/content/docs/fetch-options/2.20.0.html index 360d5d61d9..d62ae0bac7 100644 --- a/external/docs/content/docs/fetch-options/2.20.0.html +++ b/external/docs/content/docs/fetch-options/2.20.0.html @@ -54,7 +54,7 @@
Deepen or shorten the history of a shallow repository to include all reachable commits after <date>.
Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. @@ -109,7 +109,7 @@
When git fetch is used with <src>:<dst> refspec it may
refuse to update the local branch as discussed
-in the <refspec> part below.
+in the <refspec> part below.
This option overrides that check.
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the specified refspec (can be given more than once) to map the diff --git a/external/docs/content/docs/fetch-options/2.22.0.html b/external/docs/content/docs/fetch-options/2.22.0.html index 3496cd3eda..f0794af20d 100644 --- a/external/docs/content/docs/fetch-options/2.22.0.html +++ b/external/docs/content/docs/fetch-options/2.22.0.html @@ -49,7 +49,7 @@
Deepen or shorten the history of a shallow repository to include all reachable commits after <date>.
Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. @@ -104,7 +104,7 @@
When git fetch is used with <src>:<dst> refspec it may
refuse to update the local branch as discussed
-in the <refspec> part below.
+in the <refspec> part below.
This option overrides that check.
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the specified refspec (can be given more than once) to map the diff --git a/external/docs/content/docs/fetch-options/2.23.0.html b/external/docs/content/docs/fetch-options/2.23.0.html index 4762efb50f..e65d704d92 100644 --- a/external/docs/content/docs/fetch-options/2.23.0.html +++ b/external/docs/content/docs/fetch-options/2.23.0.html @@ -48,7 +48,7 @@
Deepen or shorten the history of a shallow repository to include all reachable commits after <date>.
Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. @@ -103,7 +103,7 @@
When git fetch is used with <src>:<dst> refspec it may
refuse to update the local branch as discussed
-in the <refspec> part below.
+in the <refspec> part below.
This option overrides that check.
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the specified refspec (can be given more than once) to map the diff --git a/external/docs/content/docs/fetch-options/2.24.0.html b/external/docs/content/docs/fetch-options/2.24.0.html index 857d066984..767201522b 100644 --- a/external/docs/content/docs/fetch-options/2.24.0.html +++ b/external/docs/content/docs/fetch-options/2.24.0.html @@ -48,7 +48,7 @@
Deepen or shorten the history of a shallow repository to include all reachable commits after <date>.
Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. @@ -103,7 +103,7 @@
When git fetch is used with <src>:<dst> refspec it may
refuse to update the local branch as discussed
-in the <refspec> part below.
+in the <refspec> part below.
This option overrides that check.
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the specified refspec (can be given more than once) to map the diff --git a/external/docs/content/docs/fetch-options/2.25.0.html b/external/docs/content/docs/fetch-options/2.25.0.html index a2afe506c8..a8ce37e63f 100644 --- a/external/docs/content/docs/fetch-options/2.25.0.html +++ b/external/docs/content/docs/fetch-options/2.25.0.html @@ -44,7 +44,7 @@
Deepen or shorten the history of a shallow repository to include all reachable commits after <date>.
Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. @@ -99,7 +99,7 @@
When git fetch is used with <src>:<dst> refspec it may
refuse to update the local branch as discussed
-in the <refspec> part below.
+in the <refspec> part below.
This option overrides that check.
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the specified refspec (can be given more than once) to map the diff --git a/external/docs/content/docs/fetch-options/2.25.1.html b/external/docs/content/docs/fetch-options/2.25.1.html index 53d98e336f..4dcfe6f48b 100644 --- a/external/docs/content/docs/fetch-options/2.25.1.html +++ b/external/docs/content/docs/fetch-options/2.25.1.html @@ -52,7 +52,7 @@
Deepen or shorten the history of a shallow repository to include all reachable commits after <date>.
Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. @@ -107,7 +107,7 @@
When git fetch is used with <src>:<dst> refspec it may
refuse to update the local branch as discussed
-in the <refspec> part below.
+in the <refspec> part below.
This option overrides that check.
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the
specified refspec (can be given more than once) to map the
refs to remote-tracking branches, instead of the values of
remote.*.fetch configuration variables for the remote
-repository. Providing an empty <refspec> to the
+repository. Providing an empty <refspec> to the
--refmap option causes Git to ignore the configured
refspecs and rely entirely on the refspecs supplied as
command-line arguments. See section on "Configured Remote-tracking
diff --git a/external/docs/content/docs/fetch-options/2.27.0.html b/external/docs/content/docs/fetch-options/2.27.0.html
index 91e3bb3647..52be4b0905 100644
--- a/external/docs/content/docs/fetch-options/2.27.0.html
+++ b/external/docs/content/docs/fetch-options/2.27.0.html
@@ -47,7 +47,7 @@
Deepen or shorten the history of a shallow repository to include all reachable commits after <date>.
Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. @@ -102,7 +102,7 @@
When git fetch is used with <src>:<dst> refspec it may
refuse to update the local branch as discussed
-in the <refspec> part below.
+in the <refspec> part below.
This option overrides that check.
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the
specified refspec (can be given more than once) to map the
refs to remote-tracking branches, instead of the values of
remote.*.fetch configuration variables for the remote
-repository. Providing an empty <refspec> to the
+repository. Providing an empty <refspec> to the
--refmap option causes Git to ignore the configured
refspecs and rely entirely on the refspecs supplied as
command-line arguments. See section on "Configured Remote-tracking
diff --git a/external/docs/content/docs/fetch-options/2.29.0.html b/external/docs/content/docs/fetch-options/2.29.0.html
index 903ee85635..119612e3a3 100644
--- a/external/docs/content/docs/fetch-options/2.29.0.html
+++ b/external/docs/content/docs/fetch-options/2.29.0.html
@@ -57,7 +57,7 @@
Deepen or shorten the history of a shallow repository to include all reachable commits after <date>.
Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. @@ -120,7 +120,7 @@
When git fetch is used with <src>:<dst> refspec it may
refuse to update the local branch as discussed
-in the <refspec> part below.
+in the <refspec> part below.
This option overrides that check.
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the
specified refspec (can be given more than once) to map the
refs to remote-tracking branches, instead of the values of
remote.*.fetch configuration variables for the remote
-repository. Providing an empty <refspec> to the
+repository. Providing an empty <refspec> to the
--refmap option causes Git to ignore the configured
refspecs and rely entirely on the refspecs supplied as
command-line arguments. See section on "Configured Remote-tracking
diff --git a/external/docs/content/docs/fetch-options/2.31.0.html b/external/docs/content/docs/fetch-options/2.31.0.html
index cd3f15f882..410498aa2a 100644
--- a/external/docs/content/docs/fetch-options/2.31.0.html
+++ b/external/docs/content/docs/fetch-options/2.31.0.html
@@ -57,7 +57,7 @@
Deepen or shorten the history of a shallow repository to include all reachable commits after <date>.
Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. @@ -120,7 +120,7 @@
When git fetch is used with <src>:<dst> refspec it may
refuse to update the local branch as discussed
-in the <refspec> part below.
+in the <refspec> part below.
This option overrides that check.
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the
specified refspec (can be given more than once) to map the
refs to remote-tracking branches, instead of the values of
remote.*.fetch configuration variables for the remote
-repository. Providing an empty <refspec> to the
+repository. Providing an empty <refspec> to the
--refmap option causes Git to ignore the configured
refspecs and rely entirely on the refspecs supplied as
command-line arguments. See section on "Configured Remote-tracking
diff --git a/external/docs/content/docs/fetch-options/2.32.0.html b/external/docs/content/docs/fetch-options/2.32.0.html
index 00c9b58683..73e1839fc5 100644
--- a/external/docs/content/docs/fetch-options/2.32.0.html
+++ b/external/docs/content/docs/fetch-options/2.32.0.html
@@ -56,7 +56,7 @@
Deepen or shorten the history of a shallow repository to include all reachable commits after <date>.
Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. @@ -119,7 +119,7 @@
When git fetch is used with <src>:<dst> refspec it may
refuse to update the local branch as discussed
-in the <refspec> part below.
+in the <refspec> part below.
This option overrides that check.
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the
specified refspec (can be given more than once) to map the
refs to remote-tracking branches, instead of the values of
remote.*.fetch configuration variables for the remote
-repository. Providing an empty <refspec> to the
+repository. Providing an empty <refspec> to the
--refmap option causes Git to ignore the configured
refspecs and rely entirely on the refspecs supplied as
command-line arguments. See section on "Configured Remote-tracking
diff --git a/external/docs/content/docs/fetch-options/2.33.0.html b/external/docs/content/docs/fetch-options/2.33.0.html
index 1a9beca0c4..bfa031680b 100644
--- a/external/docs/content/docs/fetch-options/2.33.0.html
+++ b/external/docs/content/docs/fetch-options/2.33.0.html
@@ -75,7 +75,7 @@
Deepen or shorten the history of a shallow repository to include all reachable commits after <date>.
Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. @@ -149,7 +149,7 @@
When git fetch is used with <src>:<dst> refspec it may
refuse to update the local branch as discussed
-in the <refspec> part below.
+in the <refspec> part below.
This option overrides that check.
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the
specified refspec (can be given more than once) to map the
refs to remote-tracking branches, instead of the values of
remote.*.fetch configuration variables for the remote
-repository. Providing an empty <refspec> to the
+repository. Providing an empty <refspec> to the
--refmap option causes Git to ignore the configured
refspecs and rely entirely on the refspecs supplied as
command-line arguments. See section on "Configured Remote-tracking
diff --git a/external/docs/content/docs/fetch-options/2.36.0.html b/external/docs/content/docs/fetch-options/2.36.0.html
index 6943240ac0..5509a987c6 100644
--- a/external/docs/content/docs/fetch-options/2.36.0.html
+++ b/external/docs/content/docs/fetch-options/2.36.0.html
@@ -80,7 +80,7 @@
Deepen or shorten the history of a shallow repository to include all reachable commits after <date>.
Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. @@ -155,7 +155,7 @@
When git fetch is used with <src>:<dst> refspec it may
refuse to update the local branch as discussed
-in the <refspec> part below.
+in the <refspec> part below.
This option overrides that check.
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the
specified refspec (can be given more than once) to map the
refs to remote-tracking branches, instead of the values of
remote.*.fetch configuration variables for the remote
-repository. Providing an empty <refspec> to the
+repository. Providing an empty <refspec> to the
--refmap option causes Git to ignore the configured
refspecs and rely entirely on the refspecs supplied as
command-line arguments. See section on "Configured Remote-tracking
diff --git a/external/docs/content/docs/fetch-options/2.4.12.html b/external/docs/content/docs/fetch-options/2.4.12.html
index 75f1959d58..74815a81c4 100644
--- a/external/docs/content/docs/fetch-options/2.4.12.html
+++ b/external/docs/content/docs/fetch-options/2.4.12.html
@@ -71,8 +71,8 @@
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the specified refspec (can be given more than once) to map the diff --git a/external/docs/content/docs/fetch-options/2.41.0.html b/external/docs/content/docs/fetch-options/2.41.0.html index e7561a7ec0..0e777c9d59 100644 --- a/external/docs/content/docs/fetch-options/2.41.0.html +++ b/external/docs/content/docs/fetch-options/2.41.0.html @@ -57,7 +57,7 @@
Deepen or shorten the history of a shallow repository to include all reachable commits after <date>.
Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. @@ -141,7 +141,7 @@
When git fetch is used with <src>:<dst> refspec it may
refuse to update the local branch as discussed
-in the <refspec> part below.
+in the <refspec> part below.
This option overrides that check.
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the
specified refspec (can be given more than once) to map the
refs to remote-tracking branches, instead of the values of
remote.*.fetch configuration variables for the remote
-repository. Providing an empty <refspec> to the
+repository. Providing an empty <refspec> to the
--refmap option causes Git to ignore the configured
refspecs and rely entirely on the refspecs supplied as
command-line arguments. See section on "Configured Remote-tracking
diff --git a/external/docs/content/docs/fetch-options/2.43.0.html b/external/docs/content/docs/fetch-options/2.43.0.html
index 9101a708a3..b699833b58 100644
--- a/external/docs/content/docs/fetch-options/2.43.0.html
+++ b/external/docs/content/docs/fetch-options/2.43.0.html
@@ -56,7 +56,7 @@
Deepen or shorten the history of a shallow repository to include all reachable commits after <date>.
Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. @@ -140,7 +140,7 @@
When git fetch is used with <src>:<dst> refspec, it may
refuse to update the local branch as discussed
-in the <refspec> part below.
+in the <refspec> part below.
This option overrides that check.
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the
specified refspec (can be given more than once) to map the
refs to remote-tracking branches, instead of the values of
remote.*.fetch configuration variables for the remote
-repository. Providing an empty <refspec> to the
+repository. Providing an empty <refspec> to the
--refmap option causes Git to ignore the configured
refspecs and rely entirely on the refspecs supplied as
command-line arguments. See section on "Configured Remote-tracking
diff --git a/external/docs/content/docs/fetch-options/2.44.0.html b/external/docs/content/docs/fetch-options/2.44.0.html
index 221c400d27..785a501f33 100644
--- a/external/docs/content/docs/fetch-options/2.44.0.html
+++ b/external/docs/content/docs/fetch-options/2.44.0.html
@@ -54,7 +54,7 @@
Deepen or shorten the history of a shallow repository to include all reachable commits after <date>.
Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. @@ -138,7 +138,7 @@
When git fetch is used with <src>:<dst> refspec, it may
refuse to update the local branch as discussed
-in the <refspec> part below.
+in the <refspec> part below.
This option overrides that check.
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the
specified refspec (can be given more than once) to map the
refs to remote-tracking branches, instead of the values of
remote.*.fetch configuration variables for the remote
-repository. Providing an empty <refspec> to the
+repository. Providing an empty <refspec> to the
--refmap option causes Git to ignore the configured
refspecs and rely entirely on the refspecs supplied as
command-line arguments. See section on "Configured Remote-tracking
diff --git a/external/docs/content/docs/fetch-options/2.45.0.html b/external/docs/content/docs/fetch-options/2.45.0.html
index c424326392..0091f46fab 100644
--- a/external/docs/content/docs/fetch-options/2.45.0.html
+++ b/external/docs/content/docs/fetch-options/2.45.0.html
@@ -56,7 +56,7 @@
Deepen or shorten the history of a shallow repository to include all reachable commits after <date>.
Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. @@ -140,7 +140,7 @@
When git fetch is used with <src>:<dst> refspec, it may
refuse to update the local branch as discussed
-in the <refspec> part below.
+in the <refspec> part below.
This option overrides that check.
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the
specified refspec (can be given more than once) to map the
refs to remote-tracking branches, instead of the values of
remote.*.fetch configuration variables for the remote
-repository. Providing an empty <refspec> to the
+repository. Providing an empty <refspec> to the
--refmap option causes Git to ignore the configured
refspecs and rely entirely on the refspecs supplied as
command-line arguments. See section on "Configured Remote-tracking
diff --git a/external/docs/content/docs/fetch-options/2.46.2.html b/external/docs/content/docs/fetch-options/2.46.2.html
index 7c745e7b73..b0e42d7ef8 100644
--- a/external/docs/content/docs/fetch-options/2.46.2.html
+++ b/external/docs/content/docs/fetch-options/2.46.2.html
@@ -57,7 +57,7 @@
Deepen or shorten the history of a shallow repository to include all reachable commits after <date>.
Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. @@ -141,7 +141,7 @@
When git fetch is used with <src>:<dst> refspec, it may
refuse to update the local branch as discussed
-in the <refspec> part below.
+in the <refspec> part below.
This option overrides that check.
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the
specified refspec (can be given more than once) to map the
refs to remote-tracking branches, instead of the values of
remote.*.fetch configuration variables for the remote
-repository. Providing an empty <refspec> to the
+repository. Providing an empty <refspec> to the
--refmap option causes Git to ignore the configured
refspecs and rely entirely on the refspecs supplied as
command-line arguments. See section on "Configured Remote-tracking
diff --git a/external/docs/content/docs/fetch-options/2.48.0.html b/external/docs/content/docs/fetch-options/2.48.0.html
index 5d40c8489b..9bd0bc98fd 100644
--- a/external/docs/content/docs/fetch-options/2.48.0.html
+++ b/external/docs/content/docs/fetch-options/2.48.0.html
@@ -58,7 +58,7 @@
Deepen or shorten the history of a shallow repository to include all reachable commits after <date>.
Deepen or shorten the history of a shallow repository to exclude commits reachable from a specified remote branch or tag. @@ -142,7 +142,7 @@
When git fetch is used with <src>:<dst> refspec, it may
refuse to update the local branch as discussed
-in the <refspec> part below.
+in the <refspec> part below.
This option overrides that check.
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the
specified refspec (can be given more than once) to map the
refs to remote-tracking branches, instead of the values of
remote.*.fetch configuration variables for the remote
-repository. Providing an empty <refspec> to the
+repository. Providing an empty <refspec> to the
--refmap option causes Git to ignore the configured
refspecs and rely entirely on the refspecs supplied as
command-line arguments. See section on "Configured Remote-tracking
diff --git a/external/docs/content/docs/fetch-options/2.7.6.html b/external/docs/content/docs/fetch-options/2.7.6.html
index 99a63d8b77..6f40f41e41 100644
--- a/external/docs/content/docs/fetch-options/2.7.6.html
+++ b/external/docs/content/docs/fetch-options/2.7.6.html
@@ -70,8 +70,8 @@
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the specified refspec (can be given more than once) to map the diff --git a/external/docs/content/docs/fetch-options/2.8.6.html b/external/docs/content/docs/fetch-options/2.8.6.html index 023732ae7a..2d51138b32 100644 --- a/external/docs/content/docs/fetch-options/2.8.6.html +++ b/external/docs/content/docs/fetch-options/2.8.6.html @@ -70,8 +70,8 @@
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the specified refspec (can be given more than once) to map the diff --git a/external/docs/content/docs/fetch-options/2.9.5.html b/external/docs/content/docs/fetch-options/2.9.5.html index 8ad9959ccc..f51e41b8e2 100644 --- a/external/docs/content/docs/fetch-options/2.9.5.html +++ b/external/docs/content/docs/fetch-options/2.9.5.html @@ -71,8 +71,8 @@
Allow several <repository> and <group> arguments to be -specified. No <refspec>s may be specified.
+Allow several <repository> and <group> arguments to be +specified. No <refspec>s may be specified.
When fetching refs listed on the command line, use the specified refspec (can be given more than once) to map the diff --git a/external/docs/content/docs/git-add.html b/external/docs/content/docs/git-add.html index cb93036a4c..0462c5e5e7 100644 --- a/external/docs/content/docs/git-add.html +++ b/external/docs/content/docs/git-add.html @@ -48,7 +48,7 @@
--edit | -e] [--[no-]all | -A | --[no-]ignore-removal | [--update | -u]] [--sparse]
[--intent-to-add | -N] [--refresh] [--ignore-errors] [--ignore-missing] [--renormalize]
[--chmod=(+|-)x] [--pathspec-from-file=<file> [--pathspec-file-nul]]
- [--] [<pathspec>…]
+ [--] [<pathspec>…]
Files to add content from. Fileglobs (e.g. *.c) can
be given to add all matching files. Also a
@@ -113,7 +113,7 @@
--no-all option if you want
to add modified or new files but ignore removed ones.
For more details about the <pathspec> syntax, see the pathspec entry +
For more details about the <pathspec> syntax, see the pathspec entry in gitglossary[7].
--update Update the index just where it already has an entry matching -<pathspec>. This removes as well as modifies index entries to +<pathspec>. This removes as well as modifies index entries to match the working tree, but adds no new files.
If no <pathspec> is given when -u option is used, all
+
If no <pathspec> is given when -u option is used, all
tracked files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
--no-ignore-removal Update the index not only where the working tree has a file -matching <pathspec> but also where the index already has an +matching <pathspec> but also where the index already has an entry. This adds, modifies, and removes index entries to match the working tree.
If no <pathspec> is given when -A option is used, all
+
If no <pathspec> is given when -A option is used, all
files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index by adding new files that are unknown to the index and files modified in the working tree, but ignore files that have been removed from the working tree. This -option is a no-op when no <pathspec> is used.
+option is a no-op when no <pathspec> is used.This option is primarily to help users who are used to older
-versions of Git, whose git add <pathspec>... was a synonym
-for git add --no-all <pathspec>..., i.e. ignored removed files.
git add <pathspec>... was a synonym
+for git add --no-all <pathspec>..., i.e. ignored removed files.
-N git add [-n] [-v] [--force | -f] [--interactive | -i] [--patch | -p] [--edit | -e] [--[no-]all | --[no-]ignore-removal | [--update | -u]] [--intent-to-add | -N] [--refresh] [--ignore-errors] [--ignore-missing] - [--] [<pathspec>…]+ [--] [<pathspec>…]
Files to add content from. Fileglobs (e.g. *.c) can
be given to add all matching files. Also a
@@ -167,10 +167,10 @@
Update the index just where it already has an entry matching -<pathspec>. This removes as well as modifies index entries to +<pathspec>. This removes as well as modifies index entries to match the working tree, but adds no new files.
If no <pathspec> is given when -u option is used, all
+
If no <pathspec> is given when -u option is used, all
tracked files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index not only where the working tree has a file -matching <pathspec> but also where the index already has an +matching <pathspec> but also where the index already has an entry. This adds, modifies, and removes index entries to match the working tree.
If no <pathspec> is given when -A option is used, all
+
If no <pathspec> is given when -A option is used, all
files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index by adding new files that are unknown to the index and files modified in the working tree, but ignore files that have been removed from the working tree. This -option is a no-op when no <pathspec> is used.
+option is a no-op when no <pathspec> is used.This option is primarily to help users who are used to older -versions of Git, whose "git add <pathspec>…" was a synonym -for "git add --no-all <pathspec>…", i.e. ignored removed files.
+versions of Git, whose "git add <pathspec>…" was a synonym +for "git add --no-all <pathspec>…", i.e. ignored removed files.git add [--verbose | -v] [--dry-run | -n] [--force | -f] [--interactive | -i] [--patch | -p] [--edit | -e] [--[no-]all | --[no-]ignore-removal | [--update | -u]] [--intent-to-add | -N] [--refresh] [--ignore-errors] [--ignore-missing] - [--chmod=(+|-)x] [--] [<pathspec>…]+ [--chmod=(+|-)x] [--] [<pathspec>…]
Files to add content from. Fileglobs (e.g. *.c) can
be given to add all matching files. Also a
@@ -169,10 +169,10 @@
Update the index just where it already has an entry matching -<pathspec>. This removes as well as modifies index entries to +<pathspec>. This removes as well as modifies index entries to match the working tree, but adds no new files.
If no <pathspec> is given when -u option is used, all
+
If no <pathspec> is given when -u option is used, all
tracked files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index not only where the working tree has a file -matching <pathspec> but also where the index already has an +matching <pathspec> but also where the index already has an entry. This adds, modifies, and removes index entries to match the working tree.
If no <pathspec> is given when -A option is used, all
+
If no <pathspec> is given when -A option is used, all
files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index by adding new files that are unknown to the index and files modified in the working tree, but ignore files that have been removed from the working tree. This -option is a no-op when no <pathspec> is used.
+option is a no-op when no <pathspec> is used.This option is primarily to help users who are used to older -versions of Git, whose "git add <pathspec>…" was a synonym -for "git add --no-all <pathspec>…", i.e. ignored removed files.
+versions of Git, whose "git add <pathspec>…" was a synonym +for "git add --no-all <pathspec>…", i.e. ignored removed files.git add [--verbose | -v] [--dry-run | -n] [--force | -f] [--interactive | -i] [--patch | -p] [--edit | -e] [--[no-]all | --[no-]ignore-removal | [--update | -u]] [--intent-to-add | -N] [--refresh] [--ignore-errors] [--ignore-missing] - [--chmod=(+|-)x] [--] [<pathspec>…]+ [--chmod=(+|-)x] [--] [<pathspec>…]
Files to add content from. Fileglobs (e.g. *.c) can
be given to add all matching files. Also a
@@ -112,7 +112,7 @@
--no-all option if you want
to add modified or new files but ignore removed ones.
For more details about the <pathspec> syntax, see the pathspec entry +
For more details about the <pathspec> syntax, see the pathspec entry in gitglossary[7].
Update the index just where it already has an entry matching -<pathspec>. This removes as well as modifies index entries to +<pathspec>. This removes as well as modifies index entries to match the working tree, but adds no new files.
If no <pathspec> is given when -u option is used, all
+
If no <pathspec> is given when -u option is used, all
tracked files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index not only where the working tree has a file -matching <pathspec> but also where the index already has an +matching <pathspec> but also where the index already has an entry. This adds, modifies, and removes index entries to match the working tree.
If no <pathspec> is given when -A option is used, all
+
If no <pathspec> is given when -A option is used, all
files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index by adding new files that are unknown to the index and files modified in the working tree, but ignore files that have been removed from the working tree. This -option is a no-op when no <pathspec> is used.
+option is a no-op when no <pathspec> is used.This option is primarily to help users who are used to older -versions of Git, whose "git add <pathspec>…" was a synonym -for "git add --no-all <pathspec>…", i.e. ignored removed files.
+versions of Git, whose "git add <pathspec>…" was a synonym +for "git add --no-all <pathspec>…", i.e. ignored removed files.git add [--verbose | -v] [--dry-run | -n] [--force | -f] [--interactive | -i] [--patch | -p] [--edit | -e] [--[no-]all | --[no-]ignore-removal | [--update | -u]] [--intent-to-add | -N] [--refresh] [--ignore-errors] [--ignore-missing] [--renormalize] - [--chmod=(+|-)x] [--] [<pathspec>…]+ [--chmod=(+|-)x] [--] [<pathspec>…]
Files to add content from. Fileglobs (e.g. *.c) can
be given to add all matching files. Also a
@@ -118,7 +118,7 @@
--no-all option if you want
to add modified or new files but ignore removed ones.
For more details about the <pathspec> syntax, see the pathspec entry +
For more details about the <pathspec> syntax, see the pathspec entry in gitglossary[7].
Update the index just where it already has an entry matching -<pathspec>. This removes as well as modifies index entries to +<pathspec>. This removes as well as modifies index entries to match the working tree, but adds no new files.
If no <pathspec> is given when -u option is used, all
+
If no <pathspec> is given when -u option is used, all
tracked files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index not only where the working tree has a file -matching <pathspec> but also where the index already has an +matching <pathspec> but also where the index already has an entry. This adds, modifies, and removes index entries to match the working tree.
If no <pathspec> is given when -A option is used, all
+
If no <pathspec> is given when -A option is used, all
files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index by adding new files that are unknown to the index and files modified in the working tree, but ignore files that have been removed from the working tree. This -option is a no-op when no <pathspec> is used.
+option is a no-op when no <pathspec> is used.This option is primarily to help users who are used to older -versions of Git, whose "git add <pathspec>…" was a synonym -for "git add --no-all <pathspec>…", i.e. ignored removed files.
+versions of Git, whose "git add <pathspec>…" was a synonym +for "git add --no-all <pathspec>…", i.e. ignored removed files.git add [--verbose | -v] [--dry-run | -n] [--force | -f] [--interactive | -i] [--patch | -p] [--edit | -e] [--[no-]all | --[no-]ignore-removal | [--update | -u]] [--intent-to-add | -N] [--refresh] [--ignore-errors] [--ignore-missing] [--renormalize] - [--chmod=(+|-)x] [--] [<pathspec>…]+ [--chmod=(+|-)x] [--] [<pathspec>…]
Files to add content from. Fileglobs (e.g. *.c) can
be given to add all matching files. Also a
@@ -129,7 +129,7 @@
--no-all option if you want
to add modified or new files but ignore removed ones.
For more details about the <pathspec> syntax, see the pathspec entry +
For more details about the <pathspec> syntax, see the pathspec entry in gitglossary[7].
Update the index just where it already has an entry matching -<pathspec>. This removes as well as modifies index entries to +<pathspec>. This removes as well as modifies index entries to match the working tree, but adds no new files.
If no <pathspec> is given when -u option is used, all
+
If no <pathspec> is given when -u option is used, all
tracked files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index not only where the working tree has a file -matching <pathspec> but also where the index already has an +matching <pathspec> but also where the index already has an entry. This adds, modifies, and removes index entries to match the working tree.
If no <pathspec> is given when -A option is used, all
+
If no <pathspec> is given when -A option is used, all
files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index by adding new files that are unknown to the index and files modified in the working tree, but ignore files that have been removed from the working tree. This -option is a no-op when no <pathspec> is used.
+option is a no-op when no <pathspec> is used.This option is primarily to help users who are used to older -versions of Git, whose "git add <pathspec>…" was a synonym -for "git add --no-all <pathspec>…", i.e. ignored removed files.
+versions of Git, whose "git add <pathspec>…" was a synonym +for "git add --no-all <pathspec>…", i.e. ignored removed files.git add [--verbose | -v] [--dry-run | -n] [--force | -f] [--interactive | -i] [--patch | -p] [--edit | -e] [--[no-]all | --[no-]ignore-removal | [--update | -u]] [--intent-to-add | -N] [--refresh] [--ignore-errors] [--ignore-missing] [--renormalize] - [--chmod=(+|-)x] [--] [<pathspec>…]+ [--chmod=(+|-)x] [--] [<pathspec>…]
Files to add content from. Fileglobs (e.g. *.c) can
be given to add all matching files. Also a
@@ -115,7 +115,7 @@
--no-all option if you want
to add modified or new files but ignore removed ones.
For more details about the <pathspec> syntax, see the pathspec entry +
For more details about the <pathspec> syntax, see the pathspec entry in gitglossary[7].
Update the index just where it already has an entry matching -<pathspec>. This removes as well as modifies index entries to +<pathspec>. This removes as well as modifies index entries to match the working tree, but adds no new files.
If no <pathspec> is given when -u option is used, all
+
If no <pathspec> is given when -u option is used, all
tracked files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index not only where the working tree has a file -matching <pathspec> but also where the index already has an +matching <pathspec> but also where the index already has an entry. This adds, modifies, and removes index entries to match the working tree.
If no <pathspec> is given when -A option is used, all
+
If no <pathspec> is given when -A option is used, all
files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index by adding new files that are unknown to the index and files modified in the working tree, but ignore files that have been removed from the working tree. This -option is a no-op when no <pathspec> is used.
+option is a no-op when no <pathspec> is used.This option is primarily to help users who are used to older -versions of Git, whose "git add <pathspec>…" was a synonym -for "git add --no-all <pathspec>…", i.e. ignored removed files.
+versions of Git, whose "git add <pathspec>…" was a synonym +for "git add --no-all <pathspec>…", i.e. ignored removed files.git add [--verbose | -v] [--dry-run | -n] [--force | -f] [--interactive | -i] [--patch | -p] [--edit | -e] [--[no-]all | --[no-]ignore-removal | [--update | -u]] [--intent-to-add | -N] [--refresh] [--ignore-errors] [--ignore-missing] [--renormalize] - [--chmod=(+|-)x] [--] [<pathspec>…]+ [--chmod=(+|-)x] [--] [<pathspec>…]
Files to add content from. Fileglobs (e.g. *.c) can
be given to add all matching files. Also a
@@ -124,7 +124,7 @@
--no-all option if you want
to add modified or new files but ignore removed ones.
For more details about the <pathspec> syntax, see the pathspec entry +
For more details about the <pathspec> syntax, see the pathspec entry in gitglossary[7].
Update the index just where it already has an entry matching -<pathspec>. This removes as well as modifies index entries to +<pathspec>. This removes as well as modifies index entries to match the working tree, but adds no new files.
If no <pathspec> is given when -u option is used, all
+
If no <pathspec> is given when -u option is used, all
tracked files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index not only where the working tree has a file -matching <pathspec> but also where the index already has an +matching <pathspec> but also where the index already has an entry. This adds, modifies, and removes index entries to match the working tree.
If no <pathspec> is given when -A option is used, all
+
If no <pathspec> is given when -A option is used, all
files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index by adding new files that are unknown to the index and files modified in the working tree, but ignore files that have been removed from the working tree. This -option is a no-op when no <pathspec> is used.
+option is a no-op when no <pathspec> is used.This option is primarily to help users who are used to older -versions of Git, whose "git add <pathspec>…" was a synonym -for "git add --no-all <pathspec>…", i.e. ignored removed files.
+versions of Git, whose "git add <pathspec>…" was a synonym +for "git add --no-all <pathspec>…", i.e. ignored removed files.Files to add content from. Fileglobs (e.g. *.c) can
be given to add all matching files. Also a
@@ -163,7 +163,7 @@
--no-all option if you want
to add modified or new files but ignore removed ones.
For more details about the <pathspec> syntax, see the pathspec entry +
For more details about the <pathspec> syntax, see the pathspec entry in gitglossary[7].
Update the index just where it already has an entry matching -<pathspec>. This removes as well as modifies index entries to +<pathspec>. This removes as well as modifies index entries to match the working tree, but adds no new files.
If no <pathspec> is given when -u option is used, all
+
If no <pathspec> is given when -u option is used, all
tracked files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index not only where the working tree has a file -matching <pathspec> but also where the index already has an +matching <pathspec> but also where the index already has an entry. This adds, modifies, and removes index entries to match the working tree.
If no <pathspec> is given when -A option is used, all
+
If no <pathspec> is given when -A option is used, all
files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index by adding new files that are unknown to the index and files modified in the working tree, but ignore files that have been removed from the working tree. This -option is a no-op when no <pathspec> is used.
+option is a no-op when no <pathspec> is used.This option is primarily to help users who are used to older -versions of Git, whose "git add <pathspec>…" was a synonym -for "git add --no-all <pathspec>…", i.e. ignored removed files.
+versions of Git, whose "git add <pathspec>…" was a synonym +for "git add --no-all <pathspec>…", i.e. ignored removed files.git add [--verbose | -v] [--dry-run | -n] [--force | -f] [--interactive | -i] [--patch | -p] [--edit | -e] [--[no-]all | --[no-]ignore-removal | [--update | -u]] [--intent-to-add | -N] [--refresh] [--ignore-errors] [--ignore-missing] - [--] [<pathspec>…]+ [--] [<pathspec>…]
Files to add content from. Fileglobs (e.g. *.c) can
be given to add all matching files. Also a
@@ -165,10 +165,10 @@
Update the index just where it already has an entry matching -<pathspec>. This removes as well as modifies index entries to +<pathspec>. This removes as well as modifies index entries to match the working tree, but adds no new files.
If no <pathspec> is given when -u option is used, all
+
If no <pathspec> is given when -u option is used, all
tracked files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index not only where the working tree has a file -matching <pathspec> but also where the index already has an +matching <pathspec> but also where the index already has an entry. This adds, modifies, and removes index entries to match the working tree.
If no <pathspec> is given when -A option is used, all
+
If no <pathspec> is given when -A option is used, all
files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index by adding new files that are unknown to the index and files modified in the working tree, but ignore files that have been removed from the working tree. This -option is a no-op when no <pathspec> is used.
+option is a no-op when no <pathspec> is used.This option is primarily to help users who are used to older -versions of Git, whose "git add <pathspec>…" was a synonym -for "git add --no-all <pathspec>…", i.e. ignored removed files.
+versions of Git, whose "git add <pathspec>…" was a synonym +for "git add --no-all <pathspec>…", i.e. ignored removed files.Files to add content from. Fileglobs (e.g. *.c) can
be given to add all matching files. Also a
@@ -137,7 +137,7 @@
--no-all option if you want
to add modified or new files but ignore removed ones.
For more details about the <pathspec> syntax, see the pathspec entry +
For more details about the <pathspec> syntax, see the pathspec entry in gitglossary[7].
Update the index just where it already has an entry matching -<pathspec>. This removes as well as modifies index entries to +<pathspec>. This removes as well as modifies index entries to match the working tree, but adds no new files.
If no <pathspec> is given when -u option is used, all
+
If no <pathspec> is given when -u option is used, all
tracked files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index not only where the working tree has a file -matching <pathspec> but also where the index already has an +matching <pathspec> but also where the index already has an entry. This adds, modifies, and removes index entries to match the working tree.
If no <pathspec> is given when -A option is used, all
+
If no <pathspec> is given when -A option is used, all
files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index by adding new files that are unknown to the index and files modified in the working tree, but ignore files that have been removed from the working tree. This -option is a no-op when no <pathspec> is used.
+option is a no-op when no <pathspec> is used.This option is primarily to help users who are used to older -versions of Git, whose "git add <pathspec>…" was a synonym -for "git add --no-all <pathspec>…", i.e. ignored removed files.
+versions of Git, whose "git add <pathspec>…" was a synonym +for "git add --no-all <pathspec>…", i.e. ignored removed files.Files to add content from. Fileglobs (e.g. *.c) can
be given to add all matching files. Also a
@@ -114,7 +114,7 @@
--no-all option if you want
to add modified or new files but ignore removed ones.
For more details about the <pathspec> syntax, see the pathspec entry +
For more details about the <pathspec> syntax, see the pathspec entry in gitglossary[7].
Update the index just where it already has an entry matching -<pathspec>. This removes as well as modifies index entries to +<pathspec>. This removes as well as modifies index entries to match the working tree, but adds no new files.
If no <pathspec> is given when -u option is used, all
+
If no <pathspec> is given when -u option is used, all
tracked files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index not only where the working tree has a file -matching <pathspec> but also where the index already has an +matching <pathspec> but also where the index already has an entry. This adds, modifies, and removes index entries to match the working tree.
If no <pathspec> is given when -A option is used, all
+
If no <pathspec> is given when -A option is used, all
files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index by adding new files that are unknown to the index and files modified in the working tree, but ignore files that have been removed from the working tree. This -option is a no-op when no <pathspec> is used.
+option is a no-op when no <pathspec> is used.This option is primarily to help users who are used to older -versions of Git, whose "git add <pathspec>…" was a synonym -for "git add --no-all <pathspec>…", i.e. ignored removed files.
+versions of Git, whose "git add <pathspec>…" was a synonym +for "git add --no-all <pathspec>…", i.e. ignored removed files.Files to add content from. Fileglobs (e.g. *.c) can
be given to add all matching files. Also a
@@ -123,7 +123,7 @@
--no-all option if you want
to add modified or new files but ignore removed ones.
For more details about the <pathspec> syntax, see the pathspec entry +
For more details about the <pathspec> syntax, see the pathspec entry in gitglossary[7].
Update the index just where it already has an entry matching -<pathspec>. This removes as well as modifies index entries to +<pathspec>. This removes as well as modifies index entries to match the working tree, but adds no new files.
If no <pathspec> is given when -u option is used, all
+
If no <pathspec> is given when -u option is used, all
tracked files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index not only where the working tree has a file -matching <pathspec> but also where the index already has an +matching <pathspec> but also where the index already has an entry. This adds, modifies, and removes index entries to match the working tree.
If no <pathspec> is given when -A option is used, all
+
If no <pathspec> is given when -A option is used, all
files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index by adding new files that are unknown to the index and files modified in the working tree, but ignore files that have been removed from the working tree. This -option is a no-op when no <pathspec> is used.
+option is a no-op when no <pathspec> is used.This option is primarily to help users who are used to older -versions of Git, whose "git add <pathspec>…" was a synonym -for "git add --no-all <pathspec>…", i.e. ignored removed files.
+versions of Git, whose "git add <pathspec>…" was a synonym +for "git add --no-all <pathspec>…", i.e. ignored removed files.git add [--verbose | -v] [--dry-run | -n] [--force | -f] [--interactive | -i] [--patch | -p] [--edit | -e] [--[no-]all | --[no-]ignore-removal | [--update | -u]] [--intent-to-add | -N] [--refresh] [--ignore-errors] [--ignore-missing] - [--] [<pathspec>…]+ [--] [<pathspec>…]
Files to add content from. Fileglobs (e.g. *.c) can
be given to add all matching files. Also a
@@ -168,10 +168,10 @@
Update the index just where it already has an entry matching -<pathspec>. This removes as well as modifies index entries to +<pathspec>. This removes as well as modifies index entries to match the working tree, but adds no new files.
If no <pathspec> is given when -u option is used, all
+
If no <pathspec> is given when -u option is used, all
tracked files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index not only where the working tree has a file -matching <pathspec> but also where the index already has an +matching <pathspec> but also where the index already has an entry. This adds, modifies, and removes index entries to match the working tree.
If no <pathspec> is given when -A option is used, all
+
If no <pathspec> is given when -A option is used, all
files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index by adding new files that are unknown to the index and files modified in the working tree, but ignore files that have been removed from the working tree. This -option is a no-op when no <pathspec> is used.
+option is a no-op when no <pathspec> is used.This option is primarily to help users who are used to older -versions of Git, whose "git add <pathspec>…" was a synonym -for "git add --no-all <pathspec>…", i.e. ignored removed files.
+versions of Git, whose "git add <pathspec>…" was a synonym +for "git add --no-all <pathspec>…", i.e. ignored removed files.Files to add content from. Fileglobs (e.g. *.c) can
be given to add all matching files. Also a
@@ -126,7 +126,7 @@
--no-all option if you want
to add modified or new files but ignore removed ones.
For more details about the <pathspec> syntax, see the pathspec entry +
For more details about the <pathspec> syntax, see the pathspec entry in gitglossary[7].
Update the index just where it already has an entry matching -<pathspec>. This removes as well as modifies index entries to +<pathspec>. This removes as well as modifies index entries to match the working tree, but adds no new files.
If no <pathspec> is given when -u option is used, all
+
If no <pathspec> is given when -u option is used, all
tracked files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index not only where the working tree has a file -matching <pathspec> but also where the index already has an +matching <pathspec> but also where the index already has an entry. This adds, modifies, and removes index entries to match the working tree.
If no <pathspec> is given when -A option is used, all
+
If no <pathspec> is given when -A option is used, all
files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index by adding new files that are unknown to the index and files modified in the working tree, but ignore files that have been removed from the working tree. This -option is a no-op when no <pathspec> is used.
+option is a no-op when no <pathspec> is used.This option is primarily to help users who are used to older -versions of Git, whose "git add <pathspec>…" was a synonym -for "git add --no-all <pathspec>…", i.e. ignored removed files.
+versions of Git, whose "git add <pathspec>…" was a synonym +for "git add --no-all <pathspec>…", i.e. ignored removed files.Files to add content from. Fileglobs (e.g. *.c) can
be given to add all matching files. Also a
@@ -123,7 +123,7 @@
--no-all option if you want
to add modified or new files but ignore removed ones.
For more details about the <pathspec> syntax, see the pathspec entry +
For more details about the <pathspec> syntax, see the pathspec entry in gitglossary[7].
Update the index just where it already has an entry matching -<pathspec>. This removes as well as modifies index entries to +<pathspec>. This removes as well as modifies index entries to match the working tree, but adds no new files.
If no <pathspec> is given when -u option is used, all
+
If no <pathspec> is given when -u option is used, all
tracked files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index not only where the working tree has a file -matching <pathspec> but also where the index already has an +matching <pathspec> but also where the index already has an entry. This adds, modifies, and removes index entries to match the working tree.
If no <pathspec> is given when -A option is used, all
+
If no <pathspec> is given when -A option is used, all
files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index by adding new files that are unknown to the index and files modified in the working tree, but ignore files that have been removed from the working tree. This -option is a no-op when no <pathspec> is used.
+option is a no-op when no <pathspec> is used.This option is primarily to help users who are used to older -versions of Git, whose "git add <pathspec>…" was a synonym -for "git add --no-all <pathspec>…", i.e. ignored removed files.
+versions of Git, whose "git add <pathspec>…" was a synonym +for "git add --no-all <pathspec>…", i.e. ignored removed files.Files to add content from. Fileglobs (e.g. *.c) can
be given to add all matching files. Also a
@@ -116,7 +116,7 @@
--no-all option if you want
to add modified or new files but ignore removed ones.
For more details about the <pathspec> syntax, see the pathspec entry +
For more details about the <pathspec> syntax, see the pathspec entry in gitglossary[7].
Update the index just where it already has an entry matching -<pathspec>. This removes as well as modifies index entries to +<pathspec>. This removes as well as modifies index entries to match the working tree, but adds no new files.
If no <pathspec> is given when -u option is used, all
+
If no <pathspec> is given when -u option is used, all
tracked files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index not only where the working tree has a file -matching <pathspec> but also where the index already has an +matching <pathspec> but also where the index already has an entry. This adds, modifies, and removes index entries to match the working tree.
If no <pathspec> is given when -A option is used, all
+
If no <pathspec> is given when -A option is used, all
files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index by adding new files that are unknown to the index and files modified in the working tree, but ignore files that have been removed from the working tree. This -option is a no-op when no <pathspec> is used.
+option is a no-op when no <pathspec> is used.This option is primarily to help users who are used to older -versions of Git, whose "git add <pathspec>…" was a synonym -for "git add --no-all <pathspec>…", i.e. ignored removed files.
+versions of Git, whose "git add <pathspec>…" was a synonym +for "git add --no-all <pathspec>…", i.e. ignored removed files.Files to add content from. Fileglobs (e.g. *.c) can
be given to add all matching files. Also a
@@ -120,7 +120,7 @@
--no-all option if you want
to add modified or new files but ignore removed ones.
For more details about the <pathspec> syntax, see the pathspec entry +
For more details about the <pathspec> syntax, see the pathspec entry in gitglossary[7].
Update the index just where it already has an entry matching -<pathspec>. This removes as well as modifies index entries to +<pathspec>. This removes as well as modifies index entries to match the working tree, but adds no new files.
If no <pathspec> is given when -u option is used, all
+
If no <pathspec> is given when -u option is used, all
tracked files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index not only where the working tree has a file -matching <pathspec> but also where the index already has an +matching <pathspec> but also where the index already has an entry. This adds, modifies, and removes index entries to match the working tree.
If no <pathspec> is given when -A option is used, all
+
If no <pathspec> is given when -A option is used, all
files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index by adding new files that are unknown to the index and files modified in the working tree, but ignore files that have been removed from the working tree. This -option is a no-op when no <pathspec> is used.
+option is a no-op when no <pathspec> is used.This option is primarily to help users who are used to older -versions of Git, whose "git add <pathspec>…" was a synonym -for "git add --no-all <pathspec>…", i.e. ignored removed files.
+versions of Git, whose "git add <pathspec>…" was a synonym +for "git add --no-all <pathspec>…", i.e. ignored removed files.--edit | -e] [--[no-]all | -A | --[no-]ignore-removal | [--update | -u]] [--sparse]
[--intent-to-add | -N] [--refresh] [--ignore-errors] [--ignore-missing] [--renormalize]
[--chmod=(+|-)x] [--pathspec-from-file=<file> [--pathspec-file-nul]]
- [--] [<pathspec>…]
+ [--] [<pathspec>…]
Files to add content from. Fileglobs (e.g. *.c) can
be given to add all matching files. Also a
@@ -118,7 +118,7 @@
--no-all option if you want
to add modified or new files but ignore removed ones.
For more details about the <pathspec> syntax, see the pathspec entry +
For more details about the <pathspec> syntax, see the pathspec entry in gitglossary[7].
--update Update the index just where it already has an entry matching -<pathspec>. This removes as well as modifies index entries to +<pathspec>. This removes as well as modifies index entries to match the working tree, but adds no new files.
If no <pathspec> is given when -u option is used, all
+
If no <pathspec> is given when -u option is used, all
tracked files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
--no-ignore-removal Update the index not only where the working tree has a file -matching <pathspec> but also where the index already has an +matching <pathspec> but also where the index already has an entry. This adds, modifies, and removes index entries to match the working tree.
If no <pathspec> is given when -A option is used, all
+
If no <pathspec> is given when -A option is used, all
files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index by adding new files that are unknown to the index and files modified in the working tree, but ignore files that have been removed from the working tree. This -option is a no-op when no <pathspec> is used.
+option is a no-op when no <pathspec> is used.This option is primarily to help users who are used to older
-versions of Git, whose git add <pathspec>... was a synonym
-for git add --no-all <pathspec>..., i.e. ignored removed files.
git add <pathspec>... was a synonym
+for git add --no-all <pathspec>..., i.e. ignored removed files.
-N --edit | -e] [--[no-]all | -A | --[no-]ignore-removal | [--update | -u]] [--sparse]
[--intent-to-add | -N] [--refresh] [--ignore-errors] [--ignore-missing] [--renormalize]
[--chmod=(+|-)x] [--pathspec-from-file=<file> [--pathspec-file-nul]]
- [--] [<pathspec>…]
+ [--] [<pathspec>…]
Files to add content from. Fileglobs (e.g. *.c) can
be given to add all matching files. Also a
@@ -112,7 +112,7 @@
--no-all option if you want
to add modified or new files but ignore removed ones.
For more details about the <pathspec> syntax, see the pathspec entry +
For more details about the <pathspec> syntax, see the pathspec entry in gitglossary[7].
--update Update the index just where it already has an entry matching -<pathspec>. This removes as well as modifies index entries to +<pathspec>. This removes as well as modifies index entries to match the working tree, but adds no new files.
If no <pathspec> is given when -u option is used, all
+
If no <pathspec> is given when -u option is used, all
tracked files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
--no-ignore-removal Update the index not only where the working tree has a file -matching <pathspec> but also where the index already has an +matching <pathspec> but also where the index already has an entry. This adds, modifies, and removes index entries to match the working tree.
If no <pathspec> is given when -A option is used, all
+
If no <pathspec> is given when -A option is used, all
files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index by adding new files that are unknown to the index and files modified in the working tree, but ignore files that have been removed from the working tree. This -option is a no-op when no <pathspec> is used.
+option is a no-op when no <pathspec> is used.This option is primarily to help users who are used to older
-versions of Git, whose git add <pathspec>... was a synonym
-for git add --no-all <pathspec>..., i.e. ignored removed files.
git add <pathspec>... was a synonym
+for git add --no-all <pathspec>..., i.e. ignored removed files.
-N git add [--verbose | -v] [--dry-run | -n] [--force | -f] [--interactive | -i] [--patch | -p] [--edit | -e] [--[no-]all | --[no-]ignore-removal | [--update | -u]] [--intent-to-add | -N] [--refresh] [--ignore-errors] [--ignore-missing] - [--] [<pathspec>…]+ [--] [<pathspec>…]
Files to add content from. Fileglobs (e.g. *.c) can
be given to add all matching files. Also a
@@ -168,10 +168,10 @@
Update the index just where it already has an entry matching -<pathspec>. This removes as well as modifies index entries to +<pathspec>. This removes as well as modifies index entries to match the working tree, but adds no new files.
If no <pathspec> is given when -u option is used, all
+
If no <pathspec> is given when -u option is used, all
tracked files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index not only where the working tree has a file -matching <pathspec> but also where the index already has an +matching <pathspec> but also where the index already has an entry. This adds, modifies, and removes index entries to match the working tree.
If no <pathspec> is given when -A option is used, all
+
If no <pathspec> is given when -A option is used, all
files in the entire working tree are updated (old versions
of Git used to limit the update to the current directory and its
subdirectories).
Update the index by adding new files that are unknown to the index and files modified in the working tree, but ignore files that have been removed from the working tree. This -option is a no-op when no <pathspec> is used.
+option is a no-op when no <pathspec> is used.This option is primarily to help users who are used to older -versions of Git, whose "git add <pathspec>…" was a synonym -for "git add --no-all <pathspec>…", i.e. ignored removed files.
+versions of Git, whose "git add <pathspec>…" was a synonym +for "git add --no-all <pathspec>…", i.e. ignored removed files.git am [--signoff] [--keep] [--[no-]keep-cr] [--[no-]utf8]] [--no-verify] [--[no-]3way] [--interactive] [--committer-date-is-author-date] [--ignore-date] [--ignore-space-change | --ignore-whitespace] - [--whitespace=<action>] [-C<n>] [-p<n>] [--directory=<répertoire>] + [--whitespace=<action>] [-C<n>] [-p<n>] [--directory=<répertoire>] [--exclude=<path>] [--include=<path>] [--reject] [-q | --quiet] [--[no-]scissors] [-S[<idclé>]] [--patch-format=<format>] [--quoted-cr=<action>] diff --git a/external/docs/content/docs/git-am/zh_HANS-CN.html b/external/docs/content/docs/git-am/zh_HANS-CN.html index 0faf715707..ed640c35e9 100644 --- a/external/docs/content/docs/git-am/zh_HANS-CN.html +++ b/external/docs/content/docs/git-am/zh_HANS-CN.html @@ -172,7 +172,7 @@选项
git annotate [<options>] <file> [<revision>]+
git annotate [<options>] <file> [<revision>]
git annotate [<options>] <file> [<revision>]+
git annotate [<options>] <file> [<revision>]
git annotate [<options>] <file> [<revision>]+
git annotate [<options>] <file> [<revision>]
git annotate [<options>] <file> [<revision>]+
git annotate [<options>] <file> [<revision>]
git annotate [<options>] <file> [<revision>]+
git annotate [<options>] <file> [<revision>]
git annotate [<options>] <file> [<revision>]+
git annotate [<options>] <file> [<revision>]
git archimport [-h] [-v] [-o] [-a] [-f] [-T] [-D <depth>] [-t <tempdir>] - <archive>/<branch>[:<git-branch>]…+ <archive>/<branch>[:<git-branch>]…
Imports a project from one or more GNU Arch repositories. It will follow branches -and repositories within the namespaces defined by the <archive>/<branch> +and repositories within the namespaces defined by the <archive>/<branch> parameters supplied. If it cannot find the remote branch a merge comes from it will just import it as a regular commit. If it can find it, it will mark it as a merge whenever possible (see discussion below).
@@ -60,7 +60,7 @@It expects to be dealing with one project only. If it sees branches that have different roots, it will refuse to run. In that case, -edit your <archive>/<branch> parameters to define clearly the scope of the +edit your <archive>/<branch> parameters to define clearly the scope of the import.
While git archimport will try to create sensible branch names for the archives that it imports, it is also possible to specify Git branch names -manually. To do so, write a Git branch name after each <archive>/<branch> +manually. To do so, write a Git branch name after each <archive>/<branch> parameter, separated by a colon. This way, you can shorten the Arch branch names and convert Arch jargon to Git jargon, for example mapping a "PROJECT--devo--VERSION" branch to "master".
@@ -156,9 +156,9 @@Override the default tempdir.
<archive>/<branch> identifier in a format that tla log understands.
<archive>/<branch> identifier in a format that tla log understands.
git archimport [-h] [-v] [-o] [-a] [-f] [-T] [-D <depth>] [-t <tempdir>] - <archive>/<branch>[:<git-branch>]…+ <archive>/<branch>[:<git-branch>]…
Imports a project from one or more GNU Arch repositories. It will follow branches -and repositories within the namespaces defined by the <archive>/<branch> +and repositories within the namespaces defined by the <archive>/<branch> parameters supplied. If it cannot find the remote branch a merge comes from it will just import it as a regular commit. If it can find it, it will mark it as a merge whenever possible (see discussion below).
@@ -143,7 +143,7 @@It expects to be dealing with one project only. If it sees branches that have different roots, it will refuse to run. In that case, -edit your <archive>/<branch> parameters to define clearly the scope of the +edit your <archive>/<branch> parameters to define clearly the scope of the import.
While git archimport will try to create sensible branch names for the archives that it imports, it is also possible to specify Git branch names -manually. To do so, write a Git branch name after each <archive>/<branch> +manually. To do so, write a Git branch name after each <archive>/<branch> parameter, separated by a colon. This way, you can shorten the Arch branch names and convert Arch jargon to Git jargon, for example mapping a "PROJECT--devo--VERSION" branch to "master".
@@ -239,9 +239,9 @@Override the default tempdir.
<archive>/<branch> identifier in a format that tla log understands.
<archive>/<branch> identifier in a format that tla log understands.
git archimport [-h] [-v] [-o] [-a] [-f] [-T] [-D <profondeur>] [-t <répertoire-temporaire>] - <archive>/<branche>[:<branche-git>] …+ <archive>/<branche>[:<branche-git>] …
Importe un projet à partir d’un ou plusieurs dépôts de GNU Arch. Il suivra les branches et les dépôts dans les espaces de noms définis par les paramètres <archive>/<branche> fournis. S’il ne peut pas trouver la branche distante d’où provient une fusion, il l’importera simplement comme un commit normal. S’il peut la trouver, il la marquera comme une fusion chaque fois que possible (voir la discussion ci-dessous).
+Importe un projet à partir d’un ou plusieurs dépôts de GNU Arch. Il suivra les branches et les dépôts dans les espaces de noms définis par les paramètres <archive>/<branche> fournis. S’il ne peut pas trouver la branche distante d’où provient une fusion, il l’importera simplement comme un commit normal. S’il peut la trouver, il la marquera comme une fusion chaque fois que possible (voir la discussion ci-dessous).
Le script attend de vous que vous fournissiez les racines clés où il peut démarrer l’importation à partir d’un "import initial" ou d’une "étiquette" de type commit Arch. Il suivra et importera les nouvelles branches dans les racines fournies.
Il ne s’attend à traiter qu’un seul projet. S’il voit des branches qui ont des racines différentes, il refusera de se lancer. Dans ce cas, modifiez vos paramètres <archive>/<branche> pour définir clairement la portée de l’importation.
+Il ne s’attend à traiter qu’un seul projet. S’il voit des branches qui ont des racines différentes, il refusera de se lancer. Dans ce cas, modifiez vos paramètres <archive>/<branche> pour définir clairement la portée de l’importation.
git archimport utilise beaucoup tla en arrière-plan pour accéder au dépôt Arch. Assurez-vous que vous avez une version récente de tla disponible dans le chemin d’accès. tla doit connaître les dépôts que vous passez à git archimport.
Alors que git archimport essaiera de créer des noms de branches sensibles pour les archives qu’il importe, il est également possible de spécifier manuellement les noms de branches Git. Pour ce faire, écrivez un nom de branche Git après chaque paramètre <archive>/<branche>, séparé par deux points. De cette façon, vous pouvez raccourcir les noms de branches Arch et convertir le jargon Arch en jargon Git, par exemple en faisant correspondre une branche "PROJECT--devo--VERSION" à "master".
+Alors que git archimport essaiera de créer des noms de branches sensibles pour les archives qu’il importe, il est également possible de spécifier manuellement les noms de branches Git. Pour ce faire, écrivez un nom de branche Git après chaque paramètre <archive>/<branche>, séparé par deux points. De cette façon, vous pouvez raccourcir les noms de branches Arch et convertir le jargon Arch en jargon Git, par exemple en faisant correspondre une branche "PROJECT--devo--VERSION" à "master".
Il est possible d’associer plusieurs branches Arch à une branche Git ; le résultat n’aura de sens que si aucun commit n’est poussé sur la première branche, après la création de la deuxième branche. Néanmoins, cela est utile pour convertir les dépôts Arch qui ont fait l’objet d’une rotation périodique.
@@ -116,9 +116,9 @@Remplacer le répertoire temporaire par défaut.
Identificateur de <archive>/<branche> dans un format compréhensible par tla log.
Identificateur de <archive>/<branche> dans un format compréhensible par tla log.
git archive [--format=<fmt>] [--list] [--prefix=<prefix>/] [<extra>]
[-o <file> | --output=<file>] [--worktree-attributes]
- [--remote=<repo> [--exec=<git-upload-archive>]] <tree-ish>
+ [--remote=<repo> [--exec=<git-upload-archive>]] <tree-ish>
[<path>…]
Set modification time of archive entries. Without this option -the committer time is used if <tree-ish> is a commit or tag, +the committer time is used if <tree-ish> is a commit or tag, and the current time if it is a tree.
Instead of making a tar archive from the local repository, retrieve a tar archive from a remote repository. Note that the remote repository may place restrictions on which sha1 -expressions may be allowed in <tree-ish>. See +expressions may be allowed in <tree-ish>. See git-upload-archive[1] for details.
Used with --remote to specify the path to the git-upload-archive on the remote side.
-The tree or commit to produce an archive for.
git archive [--format=<fmt>] [--list] [--prefix=<prefix>/] [<extra>]
[-o <file> | --output=<file>] [--worktree-attributes]
- [--remote=<repo> [--exec=<git-upload-archive>]] <tree-ish>
+ [--remote=<repo> [--exec=<git-upload-archive>]] <tree-ish>
[<path>…]
Instead of making a tar archive from the local repository, retrieve a tar archive from a remote repository. Note that the remote repository may place restrictions on which sha1 -expressions may be allowed in <tree-ish>. See +expressions may be allowed in <tree-ish>. See git-upload-archive[1] for details.
Used with --remote to specify the path to the git-upload-archive on the remote side.
-The tree or commit to produce an archive for.
git archive [--format=<fmt>] [--list] [--prefix=<prefix>/] [<extra>]
[-o <file> | --output=<file>] [--worktree-attributes]
- [--remote=<repo> [--exec=<git-upload-archive>]] <tree-ish>
+ [--remote=<repo> [--exec=<git-upload-archive>]] <tree-ish>
[<path>…]
Instead of making a tar archive from the local repository, retrieve a tar archive from a remote repository. Note that the remote repository may place restrictions on which sha1 -expressions may be allowed in <tree-ish>. See +expressions may be allowed in <tree-ish>. See git-upload-archive[1] for details.
Used with --remote to specify the path to the git-upload-archive on the remote side.
-The tree or commit to produce an archive for.
git archive [--format=<fmt>] [--list] [--prefix=<prefix>/] [<extra>]
[-o <file> | --output=<file>] [--worktree-attributes]
- [--remote=<repo> [--exec=<git-upload-archive>]] <tree-ish>
+ [--remote=<repo> [--exec=<git-upload-archive>]] <tree-ish>
[<path>…]
Instead of making a tar archive from the local repository, retrieve a tar archive from a remote repository. Note that the remote repository may place restrictions on which sha1 -expressions may be allowed in <tree-ish>. See +expressions may be allowed in <tree-ish>. See git-upload-archive[1] for details.
Used with --remote to specify the path to the git-upload-archive on the remote side.
-The tree or commit to produce an archive for.
git archive [--format=<fmt>] [--list] [--prefix=<prefix>/] [<extra>]
[-o <file> | --output=<file>] [--worktree-attributes]
- [--remote=<repo> [--exec=<git-upload-archive>]] <tree-ish>
+ [--remote=<repo> [--exec=<git-upload-archive>]] <tree-ish>
[<path>…]
Instead of making a tar archive from the local repository, retrieve a tar archive from a remote repository. Note that the remote repository may place restrictions on which sha1 -expressions may be allowed in <tree-ish>. See +expressions may be allowed in <tree-ish>. See git-upload-archive[1] for details.
Used with --remote to specify the path to the git-upload-archive on the remote side.
-The tree or commit to produce an archive for.
git archive [--format=<fmt>] [--list] [--prefix=<prefix>/] [<extra>]
[-o <file> | --output=<file>] [--worktree-attributes]
- [--remote=<repo> [--exec=<git-upload-archive>]] <tree-ish>
+ [--remote=<repo> [--exec=<git-upload-archive>]] <tree-ish>
[<path>…]
Instead of making a tar archive from the local repository, retrieve a tar archive from a remote repository. Note that the remote repository may place restrictions on which sha1 -expressions may be allowed in <tree-ish>. See +expressions may be allowed in <tree-ish>. See git-upload-archive[1] for details.
Used with --remote to specify the path to the git-upload-archive on the remote side.
-The tree or commit to produce an archive for.
git archive [--format=<fmt>] [--list] [--prefix=<prefix>/] [<extra>]
[-o <file> | --output=<file>] [--worktree-attributes]
- [--remote=<repo> [--exec=<git-upload-archive>]] <tree-ish>
+ [--remote=<repo> [--exec=<git-upload-archive>]] <tree-ish>
[<path>…]
Set modification time of archive entries. Without this option -the committer time is used if <tree-ish> is a commit or tag, +the committer time is used if <tree-ish> is a commit or tag, and the current time if it is a tree.
Instead of making a tar archive from the local repository, retrieve a tar archive from a remote repository. Note that the remote repository may place restrictions on which sha1 -expressions may be allowed in <tree-ish>. See +expressions may be allowed in <tree-ish>. See git-upload-archive[1] for details.
Used with --remote to specify the path to the git-upload-archive on the remote side.
-The tree or commit to produce an archive for.
git archive [--format=<fmt>] [--list] [--prefix=<prefix>/] [<extra>]
[-o <file> | --output=<file>] [--worktree-attributes]
- [--remote=<repo> [--exec=<git-upload-archive>]] <tree-ish>
+ [--remote=<repo> [--exec=<git-upload-archive>]] <tree-ish>
[<path>…]
Set modification time of archive entries. Without this option -the committer time is used if <tree-ish> is a commit or tag, +the committer time is used if <tree-ish> is a commit or tag, and the current time if it is a tree.
Instead of making a tar archive from the local repository, retrieve a tar archive from a remote repository. Note that the remote repository may place restrictions on which sha1 -expressions may be allowed in <tree-ish>. See +expressions may be allowed in <tree-ish>. See git-upload-archive[1] for details.
Used with --remote to specify the path to the git-upload-archive on the remote side.
-The tree or commit to produce an archive for.
git archive [--format=<fmt>] [--list] [--prefix=<prefix>/] [<extra>]
[-o <file> | --output=<file>] [--worktree-attributes]
- [--remote=<repo> [--exec=<git-upload-archive>]] <tree-ish>
+ [--remote=<repo> [--exec=<git-upload-archive>]] <tree-ish>
[<path>…]
Set modification time of archive entries. Without this option -the committer time is used if <tree-ish> is a commit or tag, +the committer time is used if <tree-ish> is a commit or tag, and the current time if it is a tree.
Instead of making a tar archive from the local repository, retrieve a tar archive from a remote repository. Note that the remote repository may place restrictions on which sha1 -expressions may be allowed in <tree-ish>. See +expressions may be allowed in <tree-ish>. See git-upload-archive[1] for details.
Used with --remote to specify the path to the git-upload-archive on the remote side.
-The tree or commit to produce an archive for.
git archive [--format=<fmt>] [--list] [--prefix=<préfixe>/] [<extra>] [-o <fichier> | --output=<fichier>] [--worktree-attributes] - [--remote=<dépôt> [--exec=<git-upload-archive>]] <arbre-esque> + [--remote=<dépôt> [--exec=<git-upload-archive>]] <arbre-esque> [<chemin>…]
Fixer l’heure de modification des entrées de l’archive. Sans cette option, l’heure du validateur est utilisée si <arbre-esque> est un commit ou une étiquette, et l’heure actuelle s’il s’agit d’un arbre.
+Fixer l’heure de modification des entrées de l’archive. Sans cette option, l’heure du validateur est utilisée si <arbre-esque> est un commit ou une étiquette, et l’heure actuelle s’il s’agit d’un arbre.
Il peut s’agir de n’importe quelle option que le moteur de l’archiveur comprend. Voir la section suivante.
Au lieu de créer une archive tar à partir du dépôt local, récupérer une archive tar à partir d’un dépôt distant. Notez que le dépôt distant peut imposer des restrictions sur les expressions sha1 qui peuvent être autorisées dans <arbre-esque>. Voir git-upload-archive[1] pour plus de détails.
+Au lieu de créer une archive tar à partir du dépôt local, récupérer une archive tar à partir d’un dépôt distant. Notez que le dépôt distant peut imposer des restrictions sur les expressions sha1 qui peuvent être autorisées dans <arbre-esque>. Voir git-upload-archive[1] pour plus de détails.
Utilisé avec --remote pour spécifier le chemin d’accès à git-upload-archive du côté distant.
L’arbre ou le commit pour lequel produire une archive .
git bisect start [--term-(bad|new)=<term-new> --term-(good|old)=<term-old>] - [--no-checkout] [--first-parent] [<bad> [<good>...]] [--] [<pathspec>...] + [--no-checkout] [--first-parent] [<bad> [<good>...]] [--] [<pathspec>...] git bisect (bad|new|<term-new>) [<rev>] git bisect (good|old|<term-old>) [<rev>...] git bisect terms [--term-(good|old) | --term-(bad|new)] git bisect skip [(<rev>|<range>)...] -git bisect reset [<commit>] +git bisect reset [<commit>] git bisect (visualize|view) git bisect replay <logfile> git bisect log @@ -167,7 +167,7 @@Bisect reset<
$ git bisect reset <commit>+
$ git bisect reset <commit>
$ git bisect reset <commit>+
$ git bisect reset <commit>
$ git bisect reset <commit>+
$ git bisect reset <commit>
$ git bisect reset <commit>+
$ git bisect reset <commit>
$ git bisect reset <commit>+
$ git bisect reset <commit>
$ git bisect reset <commit>+
$ git bisect reset <commit>
$ git bisect reset <commit>+
$ git bisect reset <commit>
$ git bisect reset <commit>+
$ git bisect reset <commit>
$ git bisect reset <commit>+
$ git bisect reset <commit>
$ git bisect reset <commit>+
$ git bisect reset <commit>
$ git bisect reset <commit>+
$ git bisect reset <commit>
$ git bisect reset <commit>+
$ git bisect reset <commit>
$ git bisect reset <commit>+
$ git bisect reset <commit>
git bisect start [--term-(bad|new)=<term-new> --term-(good|old)=<term-old>] - [--no-checkout] [--first-parent] [<bad> [<good>...]] [--] [<pathspec>...] + [--no-checkout] [--first-parent] [<bad> [<good>...]] [--] [<pathspec>...] git bisect (bad|new|<term-new>) [<rev>] git bisect (good|old|<term-old>) [<rev>...] git bisect terms [--term-(good|old) | --term-(bad|new)] git bisect skip [(<rev>|<range>)...] -git bisect reset [<commit>] +git bisect reset [<commit>] git bisect (visualize|view) git bisect replay <logfile> git bisect log @@ -189,7 +189,7 @@Bisect reset<
$ git bisect reset <commit>+
$ git bisect reset <commit>
git bisect start [--term-(bad|new)=<term-new> --term-(good|old)=<term-old>] - [--no-checkout] [--first-parent] [<bad> [<good>...]] [--] [<pathspec>...] + [--no-checkout] [--first-parent] [<bad> [<good>...]] [--] [<pathspec>...] git bisect (bad|new|<term-new>) [<rev>] git bisect (good|old|<term-old>) [<rev>...] git bisect terms [--term-(good|old) | --term-(bad|new)] git bisect skip [(<rev>|<range>)...] -git bisect reset [<commit>] +git bisect reset [<commit>] git bisect (visualize|view) git bisect replay <logfile> git bisect log @@ -168,7 +168,7 @@Bisect reset<
$ git bisect reset <commit>+
$ git bisect reset <commit>
$ git bisect reset <commit>+
$ git bisect reset <commit>
$ git bisect reset <commit>+
$ git bisect reset <commit>
$ git bisect reset <commit>+
$ git bisect reset <commit>
git bisect start [--term-(bad|new)=<terme-nouveau> --term-(good|old)=<terme-ancien>] - [--no-checkout] [--first-parent] [<mauvais> [<bon>...]] [--] [<spéc-de-chemin>...] + [--no-checkout] [--first-parent] [<mauvais> [<bon>...]] [--] [<spéc-de-chemin>...] git bisect (bad|new|<terme-nouveau>) [<rev>] git bisect (good|old|<terme-ancien>) [<rev>...] git bisect terms [--term-good | --term-bad] git bisect skip [(<rev>|<plage>)...] -git bisect reset [<commit>] +git bisect reset [<commit>] git bisect (visualize|view) git bisect replay <fichier-journal> git bisect log @@ -140,7 +140,7 @@Bisect reset<
$ git bisect reset <commit>+
$ git bisect reset <commit>
$ git bisect reset <commit>+
$ git bisect reset <commit>
$ git bisect reset <提交>+
$ git bisect reset <提交>
gitbranch[--color[=<when>] |--no-color] [--show-current] [-v[--abbrev=<n> |--no-abbrev]] [--column[=<options>] |--no-column] [--sort=<key>] - [--merged[<commit>]] [--no-merged[<commit>]] - [--contains[<commit>]] [--no-contains[<commit>]] - [--points-at<object>] [--format=<format>] + [--merged[<commit>]] [--no-merged[<commit>]] + [--contains[<commit>]] [--no-contains[<commit>]] + [--points-at<object>] [--format=<format>] [(-r|--remotes) | (-a|--all)] [--list] [<pattern>…]gitbranch[--track[=(direct|inherit)] |--no-track] [-f] @@ -89,7 +89,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
---contains [<commit>] --contains [<commit>] Only list branches which contain <commit> (HEAD
+
Only list branches which contain <commit> (HEAD
if not specified). Implies --list.
--no-contains [<commit>] --no-contains [<commit>] Only list branches which don’t contain <commit> +
Only list branches which don’t contain <commit>
(HEAD if not specified). Implies --list.
--merged [<commit>] --merged [<commit>] Only list branches whose tips are reachable from
-<commit> (HEAD if not specified). Implies --list.
HEAD if not specified). Implies --list.
--no-merged [<commit>] --no-merged [<commit>] Only list branches whose tips are not reachable from
-<commit> (HEAD if not specified). Implies --list.
HEAD if not specified). Implies --list.
--points-at <object> --points-at <object> Only list branches of <object>.
+Only list branches of <object>.
--format <format> --contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.0.5.html b/external/docs/content/docs/git-branch/2.0.5.html
index 8940bdf2f1..e7cdd05367 100644
--- a/external/docs/content/docs/git-branch/2.0.5.html
+++ b/external/docs/content/docs/git-branch/2.0.5.html
@@ -45,7 +45,7 @@
git branch [--color[=<when>] | --no-color] [-r | -a] [--list] [-v [--abbrev=<length> | --no-abbrev]] [--column[=<options>] | --no-column] - [(--merged | --no-merged | --contains) [<commit>]] [<pattern>…] + [(--merged | --no-merged | --contains) [<commit>]] [<pattern>…] git branch [--set-upstream | --track | --no-track] [-l] [-f] <branchname> [<start-point>] git branch (--set-upstream-to=<upstream> | -u <upstream>) [<branchname>] git branch --unset-upstream [<branchname>] @@ -75,7 +75,7 @@DESCRIPTION
--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly branches not merged into -the named commit will be listed. If the <commit> argument is missing it +the named commit will be listed. If the <commit> argument is missing it defaults to HEAD (i.e. the tip of the current branch).
Open an editor and edit the text to explain what the branch is
for, to be used by various other commands (e.g. request-pull).
Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.12.5.html b/external/docs/content/docs/git-branch/2.12.5.html
index 20f58df5c1..f3d715ced9 100644
--- a/external/docs/content/docs/git-branch/2.12.5.html
+++ b/external/docs/content/docs/git-branch/2.12.5.html
@@ -42,8 +42,8 @@
git branch [--color[=<when>] | --no-color] [-r | -a] [--list] [-v [--abbrev=<length> | --no-abbrev]] [--column[=<options>] | --no-column] - [(--merged | --no-merged | --contains) [<commit>]] [--sort=<key>] - [--points-at <object>] [<pattern>…] + [(--merged | --no-merged | --contains) [<commit>]] [--sort=<key>] + [--points-at <object>] [<pattern>…] git branch [--set-upstream | --track | --no-track] [-l] [-f] <branchname> [<start-point>] git branch (--set-upstream-to=<upstream> | -u <upstream>) [<branchname>] git branch --unset-upstream [<branchname>] @@ -73,7 +73,7 @@DESCRIPTION
--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly branches not merged into -the named commit will be listed. If the <commit> argument is missing it +the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.13.7.html b/external/docs/content/docs/git-branch/2.13.7.html
index 2207e02a2b..3c1d1078ba 100644
--- a/external/docs/content/docs/git-branch/2.13.7.html
+++ b/external/docs/content/docs/git-branch/2.13.7.html
@@ -42,9 +42,9 @@
git branch [--color[=<when>] | --no-color] [-r | -a] [--list] [-v [--abbrev=<length> | --no-abbrev]] [--column[=<options>] | --no-column] [--sort=<key>] - [(--merged | --no-merged) [<commit>]] - [--contains [<commit]] [--no-contains [<commit>]] - [--points-at <object>] [--format=<format>] [<pattern>…] + [(--merged | --no-merged) [<commit>]] + [--contains [<commit]] [--no-contains [<commit>]] + [--points-at <object>] [--format=<format>] [<pattern>…] git branch [--set-upstream | --track | --no-track] [-l] [-f] <branchname> [<start-point>] git branch (--set-upstream-to=<upstream> | -u <upstream>) [<branchname>] git branch --unset-upstream [<branchname>] @@ -74,7 +74,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches which don’t contain the specified commit
(HEAD if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list,
incompatible with --no-merged.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list,
@@ -345,7 +345,7 @@
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.14.6.html b/external/docs/content/docs/git-branch/2.14.6.html
index 21d1e6aa66..350c7dd50b 100644
--- a/external/docs/content/docs/git-branch/2.14.6.html
+++ b/external/docs/content/docs/git-branch/2.14.6.html
@@ -42,9 +42,9 @@
git branch [--color[=<when>] | --no-color] [-r | -a] [--list] [-v [--abbrev=<length> | --no-abbrev]] [--column[=<options>] | --no-column] [--sort=<key>] - [(--merged | --no-merged) [<commit>]] - [--contains [<commit]] [--no-contains [<commit>]] - [--points-at <object>] [--format=<format>] [<pattern>…] + [(--merged | --no-merged) [<commit>]] + [--contains [<commit]] [--no-contains [<commit>]] + [--points-at <object>] [--format=<format>] [<pattern>…] git branch [--set-upstream | --track | --no-track] [-l] [-f] <branchname> [<start-point>] git branch (--set-upstream-to=<upstream> | -u <upstream>) [<branchname>] git branch --unset-upstream [<branchname>] @@ -74,7 +74,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches which don’t contain the specified commit
(HEAD if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list,
incompatible with --no-merged.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list,
@@ -345,7 +345,7 @@
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.15.4.html b/external/docs/content/docs/git-branch/2.15.4.html
index e6475ff094..20bd185fdb 100644
--- a/external/docs/content/docs/git-branch/2.15.4.html
+++ b/external/docs/content/docs/git-branch/2.15.4.html
@@ -42,9 +42,9 @@
git branch [--color[=<when>] | --no-color] [-r | -a] [--list] [-v [--abbrev=<length> | --no-abbrev]] [--column[=<options>] | --no-column] [--sort=<key>] - [(--merged | --no-merged) [<commit>]] - [--contains [<commit]] [--no-contains [<commit>]] - [--points-at <object>] [--format=<format>] [<pattern>…] + [(--merged | --no-merged) [<commit>]] + [--contains [<commit]] [--no-contains [<commit>]] + [--points-at <object>] [--format=<format>] [<pattern>…] git branch [--set-upstream | --track | --no-track] [-l] [-f] <branchname> [<start-point>] git branch (--set-upstream-to=<upstream> | -u <upstream>) [<branchname>] git branch --unset-upstream [<branchname>] @@ -75,7 +75,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches which don’t contain the specified commit
(HEAD if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list,
incompatible with --no-merged.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list,
@@ -358,7 +358,7 @@
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.16.6.html b/external/docs/content/docs/git-branch/2.16.6.html
index 8c22652081..dca272d3af 100644
--- a/external/docs/content/docs/git-branch/2.16.6.html
+++ b/external/docs/content/docs/git-branch/2.16.6.html
@@ -51,9 +51,9 @@
git branch [--color[=<when>] | --no-color] [-r | -a] [--list] [-v [--abbrev=<length> | --no-abbrev]] [--column[=<options>] | --no-column] [--sort=<key>] - [(--merged | --no-merged) [<commit>]] - [--contains [<commit]] [--no-contains [<commit>]] - [--points-at <object>] [--format=<format>] [<pattern>…] + [(--merged | --no-merged) [<commit>]] + [--contains [<commit]] [--no-contains [<commit>]] + [--points-at <object>] [--format=<format>] [<pattern>…] git branch [--track | --no-track] [-l] [-f] <branchname> [<start-point>] git branch (--set-upstream-to=<upstream> | -u <upstream>) [<branchname>] git branch --unset-upstream [<branchname>] @@ -84,7 +84,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches which don’t contain the specified commit
(HEAD if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list,
incompatible with --no-merged.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list,
@@ -367,7 +367,7 @@
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.18.0.html b/external/docs/content/docs/git-branch/2.18.0.html
index 9c2a7baad4..1eb2efc28a 100644
--- a/external/docs/content/docs/git-branch/2.18.0.html
+++ b/external/docs/content/docs/git-branch/2.18.0.html
@@ -49,9 +49,9 @@
git branch [--color[=<when>] | --no-color] [-r | -a] [--list] [-v [--abbrev=<length> | --no-abbrev]] [--column[=<options>] | --no-column] [--sort=<key>] - [(--merged | --no-merged) [<commit>]] - [--contains [<commit]] [--no-contains [<commit>]] - [--points-at <object>] [--format=<format>] [<pattern>…] + [(--merged | --no-merged) [<commit>]] + [--contains [<commit]] [--no-contains [<commit>]] + [--points-at <object>] [--format=<format>] [<pattern>…] git branch [--track | --no-track] [-l] [-f] <branchname> [<start-point>] git branch (--set-upstream-to=<upstream> | -u <upstream>) [<branchname>] git branch --unset-upstream [<branchname>] @@ -82,7 +82,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches which don’t contain the specified commit
(HEAD if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list,
incompatible with --no-merged.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list,
@@ -365,7 +365,7 @@
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.19.0.html b/external/docs/content/docs/git-branch/2.19.0.html
index bd210c1ba1..f33d1037fc 100644
--- a/external/docs/content/docs/git-branch/2.19.0.html
+++ b/external/docs/content/docs/git-branch/2.19.0.html
@@ -50,9 +50,9 @@
git branch [--color[=<when>] | --no-color] [-r | -a] [--list] [-v [--abbrev=<length> | --no-abbrev]] [--column[=<options>] | --no-column] [--sort=<key>] - [(--merged | --no-merged) [<commit>]] - [--contains [<commit]] [--no-contains [<commit>]] - [--points-at <object>] [--format=<format>] [<pattern>…] + [(--merged | --no-merged) [<commit>]] + [--contains [<commit]] [--no-contains [<commit>]] + [--points-at <object>] [--format=<format>] [<pattern>…] git branch [--track | --no-track] [-l] [-f] <branchname> [<start-point>] git branch (--set-upstream-to=<upstream> | -u <upstream>) [<branchname>] git branch --unset-upstream [<branchname>] @@ -83,7 +83,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches which don’t contain the specified commit
(HEAD if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list,
incompatible with --no-merged.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list,
@@ -369,7 +369,7 @@
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.20.0.html b/external/docs/content/docs/git-branch/2.20.0.html
index be77c31a65..f8b186fc14 100644
--- a/external/docs/content/docs/git-branch/2.20.0.html
+++ b/external/docs/content/docs/git-branch/2.20.0.html
@@ -49,9 +49,9 @@
git branch [--color[=<when>] | --no-color] [-r | -a] [--list] [-v [--abbrev=<length> | --no-abbrev]] [--column[=<options>] | --no-column] [--sort=<key>] - [(--merged | --no-merged) [<commit>]] - [--contains [<commit]] [--no-contains [<commit>]] - [--points-at <object>] [--format=<format>] [<pattern>…] + [(--merged | --no-merged) [<commit>]] + [--contains [<commit]] [--no-contains [<commit>]] + [--points-at <object>] [--format=<format>] [<pattern>…] git branch [--track | --no-track] [-f] <branchname> [<start-point>] git branch (--set-upstream-to=<upstream> | -u <upstream>) [<branchname>] git branch --unset-upstream [<branchname>] @@ -82,7 +82,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches which don’t contain the specified commit
(HEAD if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list,
incompatible with --no-merged.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list,
@@ -361,7 +361,7 @@
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.21.0.html b/external/docs/content/docs/git-branch/2.21.0.html
index 9322ef5720..11e17377e5 100644
--- a/external/docs/content/docs/git-branch/2.21.0.html
+++ b/external/docs/content/docs/git-branch/2.21.0.html
@@ -48,9 +48,9 @@
git branch [--color[=<when>] | --no-color] [-r | -a] [--list] [-v [--abbrev=<length> | --no-abbrev]] [--column[=<options>] | --no-column] [--sort=<key>] - [(--merged | --no-merged) [<commit>]] - [--contains [<commit]] [--no-contains [<commit>]] - [--points-at <object>] [--format=<format>] [<pattern>…] + [(--merged | --no-merged) [<commit>]] + [--contains [<commit]] [--no-contains [<commit>]] + [--points-at <object>] [--format=<format>] [<pattern>…] git branch [--track | --no-track] [-f] <branchname> [<start-point>] git branch (--set-upstream-to=<upstream> | -u <upstream>) [<branchname>] git branch --unset-upstream [<branchname>] @@ -81,7 +81,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches which don’t contain the specified commit
(HEAD if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list,
incompatible with --no-merged.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list,
@@ -360,7 +360,7 @@
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.22.0.html b/external/docs/content/docs/git-branch/2.22.0.html
index 9a0008c38b..dfcba001de 100644
--- a/external/docs/content/docs/git-branch/2.22.0.html
+++ b/external/docs/content/docs/git-branch/2.22.0.html
@@ -44,9 +44,9 @@
git branch [--color[=<when>] | --no-color] [-r | -a] [--list] [--show-current] [-v [--abbrev=<length> | --no-abbrev]] [--column[=<options>] | --no-column] [--sort=<key>] - [(--merged | --no-merged) [<commit>]] - [--contains [<commit]] [--no-contains [<commit>]] - [--points-at <object>] [--format=<format>] [<pattern>…] + [(--merged | --no-merged) [<commit>]] + [--contains [<commit]] [--no-contains [<commit>]] + [--points-at <object>] [--format=<format>] [<pattern>…] git branch [--track | --no-track] [-f] <branchname> [<start-point>] git branch (--set-upstream-to=<upstream> | -u <upstream>) [<branchname>] git branch --unset-upstream [<branchname>] @@ -77,7 +77,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches which don’t contain the specified commit
(HEAD if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list,
incompatible with --no-merged.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list,
@@ -365,7 +365,7 @@
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.22.1.html b/external/docs/content/docs/git-branch/2.22.1.html
index 2968e14e9d..b8a6993146 100644
--- a/external/docs/content/docs/git-branch/2.22.1.html
+++ b/external/docs/content/docs/git-branch/2.22.1.html
@@ -49,9 +49,9 @@
--no-contains inverts it. With --merged, only branches
merged into the named commit (i.e. the branches whose tip commits are
reachable from the named commit) will be listed. With --no-merged only
-branches not merged into the named commit will be listed. If the <commit>
+branches not merged into the named commit will be listed. If the <commit>
argument is missing it defaults to HEAD (i.e. the tip of the current
branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches which don’t contain the specified commit
(HEAD if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list,
incompatible with --no-merged.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list,
@@ -380,7 +380,7 @@
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.23.0.html b/external/docs/content/docs/git-branch/2.23.0.html
index a9d2e9c530..ecfc452fbe 100644
--- a/external/docs/content/docs/git-branch/2.23.0.html
+++ b/external/docs/content/docs/git-branch/2.23.0.html
@@ -65,9 +65,9 @@
git branch [--color[=<when>] | --no-color] [--show-current] [-v [--abbrev=<length> | --no-abbrev]] [--column[=<options>] | --no-column] [--sort=<key>] - [(--merged | --no-merged) [<commit>]] - [--contains [<commit]] [--no-contains [<commit>]] - [--points-at <object>] [--format=<format>] + [(--merged | --no-merged) [<commit>]] + [--contains [<commit]] [--no-contains [<commit>]] + [--points-at <object>] [--format=<format>] [(-r | --remotes) | (-a | --all)] [--list] [<pattern>…] git branch [--track | --no-track] [-f] <branchname> [<start-point>] @@ -108,7 +108,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches which don’t contain the specified commit
(HEAD if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list,
incompatible with --no-merged.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list,
@@ -399,7 +399,7 @@
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.28.0.html b/external/docs/content/docs/git-branch/2.28.0.html
index 2141d97d5a..d5ccd66ba9 100644
--- a/external/docs/content/docs/git-branch/2.28.0.html
+++ b/external/docs/content/docs/git-branch/2.28.0.html
@@ -45,9 +45,9 @@
git branch [--color[=<when>] | --no-color] [--show-current] [-v [--abbrev=<length> | --no-abbrev]] [--column[=<options>] | --no-column] [--sort=<key>] - [(--merged | --no-merged) [<commit>]] - [--contains [<commit>]] [--no-contains [<commit>]] - [--points-at <object>] [--format=<format>] + [(--merged | --no-merged) [<commit>]] + [--contains [<commit>]] [--no-contains [<commit>]] + [--points-at <object>] [--format=<format>] [(-r | --remotes) | (-a | --all)] [--list] [<pattern>…] git branch [--track | --no-track] [-f] <branchname> [<start-point>] @@ -88,7 +88,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches which don’t contain the specified commit
(HEAD if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list,
incompatible with --no-merged.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list,
@@ -379,7 +379,7 @@
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.29.0.html b/external/docs/content/docs/git-branch/2.29.0.html
index 5123b88dd5..b6a0e0ab25 100644
--- a/external/docs/content/docs/git-branch/2.29.0.html
+++ b/external/docs/content/docs/git-branch/2.29.0.html
@@ -47,9 +47,9 @@
git branch [--color[=<when>] | --no-color] [--show-current] [-v [--abbrev=<length> | --no-abbrev]] [--column[=<options>] | --no-column] [--sort=<key>] - [--merged [<commit>]] [--no-merged [<commit>]] - [--contains [<commit>]] [--no-contains [<commit>]] - [--points-at <object>] [--format=<format>] + [--merged [<commit>]] [--no-merged [<commit>]] + [--contains [<commit>]] [--no-contains [<commit>]] + [--points-at <object>] [--format=<format>] [(-r | --remotes) | (-a | --all)] [--list] [<pattern>…] git branch [--track | --no-track] [-f] <branchname> [<start-point>] @@ -90,7 +90,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches which don’t contain the specified commit
(HEAD if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.30.0.html b/external/docs/content/docs/git-branch/2.30.0.html
index 46f637b791..e484c6e4a6 100644
--- a/external/docs/content/docs/git-branch/2.30.0.html
+++ b/external/docs/content/docs/git-branch/2.30.0.html
@@ -53,9 +53,9 @@
git branch [--color[=<when>] | --no-color] [--show-current] [-v [--abbrev=<n> | --no-abbrev]] [--column[=<options>] | --no-column] [--sort=<key>] - [--merged [<commit>]] [--no-merged [<commit>]] - [--contains [<commit>]] [--no-contains [<commit>]] - [--points-at <object>] [--format=<format>] + [--merged [<commit>]] [--no-merged [<commit>]] + [--contains [<commit>]] [--no-contains [<commit>]] + [--points-at <object>] [--format=<format>] [(-r | --remotes) | (-a | --all)] [--list] [<pattern>…] git branch [--track | --no-track] [-f] <branchname> [<start-point>] @@ -96,7 +96,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches which don’t contain the specified commit
(HEAD if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.31.0.html b/external/docs/content/docs/git-branch/2.31.0.html
index ec61083117..41b4a06273 100644
--- a/external/docs/content/docs/git-branch/2.31.0.html
+++ b/external/docs/content/docs/git-branch/2.31.0.html
@@ -61,9 +61,9 @@
git branch [--color[=<when>] | --no-color] [--show-current] [-v [--abbrev=<n> | --no-abbrev]] [--column[=<options>] | --no-column] [--sort=<key>] - [--merged [<commit>]] [--no-merged [<commit>]] - [--contains [<commit>]] [--no-contains [<commit>]] - [--points-at <object>] [--format=<format>] + [--merged [<commit>]] [--no-merged [<commit>]] + [--contains [<commit>]] [--no-contains [<commit>]] + [--points-at <object>] [--format=<format>] [(-r | --remotes) | (-a | --all)] [--list] [<pattern>…] git branch [--track | --no-track] [-f] <branchname> [<start-point>] @@ -104,7 +104,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches which don’t contain the specified commit
(HEAD if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.33.1.html b/external/docs/content/docs/git-branch/2.33.1.html
index bfef54bdde..69445b8149 100644
--- a/external/docs/content/docs/git-branch/2.33.1.html
+++ b/external/docs/content/docs/git-branch/2.33.1.html
@@ -51,9 +51,9 @@
git branch [--color[=<when>] | --no-color] [--show-current] [-v [--abbrev=<n> | --no-abbrev]] [--column[=<options>] | --no-column] [--sort=<key>] - [--merged [<commit>]] [--no-merged [<commit>]] - [--contains [<commit>]] [--no-contains [<commit>]] - [--points-at <object>] [--format=<format>] + [--merged [<commit>]] [--no-merged [<commit>]] + [--contains [<commit>]] [--no-contains [<commit>]] + [--points-at <object>] [--format=<format>] [(-r | --remotes) | (-a | --all)] [--list] [<pattern>…] git branch [--track | --no-track] [-f] <branchname> [<start-point>] @@ -94,7 +94,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches which don’t contain the specified commit
(HEAD if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.34.0.html b/external/docs/content/docs/git-branch/2.34.0.html
index 3bfe3f2c53..0ae948b9ff 100644
--- a/external/docs/content/docs/git-branch/2.34.0.html
+++ b/external/docs/content/docs/git-branch/2.34.0.html
@@ -52,9 +52,9 @@
git branch [--color[=<when>] | --no-color] [--show-current] [-v [--abbrev=<n> | --no-abbrev]] [--column[=<options>] | --no-column] [--sort=<key>] - [--merged [<commit>]] [--no-merged [<commit>]] - [--contains [<commit>]] [--no-contains [<commit>]] - [--points-at <object>] [--format=<format>] + [--merged [<commit>]] [--no-merged [<commit>]] + [--contains [<commit>]] [--no-contains [<commit>]] + [--points-at <object>] [--format=<format>] [(-r | --remotes) | (-a | --all)] [--list] [<pattern>…] git branch [--track | --no-track] [-f] <branchname> [<start-point>] @@ -95,7 +95,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches which don’t contain the specified commit
(HEAD if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.35.0.html b/external/docs/content/docs/git-branch/2.35.0.html
index a25988e0b1..2471c730a9 100644
--- a/external/docs/content/docs/git-branch/2.35.0.html
+++ b/external/docs/content/docs/git-branch/2.35.0.html
@@ -52,9 +52,9 @@
git branch [--color[=<when>] | --no-color] [--show-current] [-v [--abbrev=<n> | --no-abbrev]] [--column[=<options>] | --no-column] [--sort=<key>] - [--merged [<commit>]] [--no-merged [<commit>]] - [--contains [<commit>]] [--no-contains [<commit>]] - [--points-at <object>] [--format=<format>] + [--merged [<commit>]] [--no-merged [<commit>]] + [--contains [<commit>]] [--no-contains [<commit>]] + [--points-at <object>] [--format=<format>] [(-r | --remotes) | (-a | --all)] [--list] [<pattern>…] git branch [--track[=(direct|inherit)] | --no-track] [-f] <branchname> [<start-point>] @@ -95,7 +95,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches which don’t contain the specified commit
(HEAD if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.36.0.html b/external/docs/content/docs/git-branch/2.36.0.html
index 6fe779f5fb..755aba43aa 100644
--- a/external/docs/content/docs/git-branch/2.36.0.html
+++ b/external/docs/content/docs/git-branch/2.36.0.html
@@ -50,9 +50,9 @@
git branch [--color[=<when>] | --no-color] [--show-current] [-v [--abbrev=<n> | --no-abbrev]] [--column[=<options>] | --no-column] [--sort=<key>] - [--merged [<commit>]] [--no-merged [<commit>]] - [--contains [<commit>]] [--no-contains [<commit>]] - [--points-at <object>] [--format=<format>] + [--merged [<commit>]] [--no-merged [<commit>]] + [--contains [<commit>]] [--no-contains [<commit>]] + [--points-at <object>] [--format=<format>] [(-r | --remotes) | (-a | --all)] [--list] [<pattern>…] git branch [--track[=(direct|inherit)] | --no-track] [-f] @@ -94,7 +94,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches which don’t contain the specified commit
(HEAD if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.37.0.html b/external/docs/content/docs/git-branch/2.37.0.html
index ad33b373b2..bbab1ad8f6 100644
--- a/external/docs/content/docs/git-branch/2.37.0.html
+++ b/external/docs/content/docs/git-branch/2.37.0.html
@@ -51,9 +51,9 @@
git branch [--color[=<when>] | --no-color] [--show-current] [-v [--abbrev=<n> | --no-abbrev]] [--column[=<options>] | --no-column] [--sort=<key>] - [--merged [<commit>]] [--no-merged [<commit>]] - [--contains [<commit>]] [--no-contains [<commit>]] - [--points-at <object>] [--format=<format>] + [--merged [<commit>]] [--no-merged [<commit>]] + [--contains [<commit>]] [--no-contains [<commit>]] + [--points-at <object>] [--format=<format>] [(-r | --remotes) | (-a | --all)] [--list] [<pattern>…] git branch [--track[=(direct|inherit)] | --no-track] [-f] @@ -95,7 +95,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches which don’t contain the specified commit
(HEAD if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.38.0.html b/external/docs/content/docs/git-branch/2.38.0.html
index b5ec9d885e..020ba3fc6e 100644
--- a/external/docs/content/docs/git-branch/2.38.0.html
+++ b/external/docs/content/docs/git-branch/2.38.0.html
@@ -52,9 +52,9 @@
git branch [--color[=<when>] | --no-color] [--show-current] [-v [--abbrev=<n> | --no-abbrev]] [--column[=<options>] | --no-column] [--sort=<key>] - [--merged [<commit>]] [--no-merged [<commit>]] - [--contains [<commit>]] [--no-contains [<commit>]] - [--points-at <object>] [--format=<format>] + [--merged [<commit>]] [--no-merged [<commit>]] + [--contains [<commit>]] [--no-contains [<commit>]] + [--points-at <object>] [--format=<format>] [(-r | --remotes) | (-a | --all)] [--list] [<pattern>…] git branch [--track[=(direct|inherit)] | --no-track] [-f] @@ -96,7 +96,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches which don’t contain the specified commit
(HEAD if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.39.3.html b/external/docs/content/docs/git-branch/2.39.3.html
index fe997304a1..6a4544ef19 100644
--- a/external/docs/content/docs/git-branch/2.39.3.html
+++ b/external/docs/content/docs/git-branch/2.39.3.html
@@ -46,9 +46,9 @@
git branch [--color[=<when>] | --no-color] [--show-current] [-v [--abbrev=<n> | --no-abbrev]] [--column[=<options>] | --no-column] [--sort=<key>] - [--merged [<commit>]] [--no-merged [<commit>]] - [--contains [<commit>]] [--no-contains [<commit>]] - [--points-at <object>] [--format=<format>] + [--merged [<commit>]] [--no-merged [<commit>]] + [--contains [<commit>]] [--no-contains [<commit>]] + [--points-at <object>] [--format=<format>] [(-r | --remotes) | (-a | --all)] [--list] [<pattern>…] git branch [--track[=(direct|inherit)] | --no-track] [-f] @@ -90,7 +90,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches which don’t contain the specified commit
(HEAD if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.4.12.html b/external/docs/content/docs/git-branch/2.4.12.html
index ce30a473e6..ebae3bfaed 100644
--- a/external/docs/content/docs/git-branch/2.4.12.html
+++ b/external/docs/content/docs/git-branch/2.4.12.html
@@ -43,7 +43,7 @@
git branch [--color[=<when>] | --no-color] [-r | -a] [--list] [-v [--abbrev=<length> | --no-abbrev]] [--column[=<options>] | --no-column] - [(--merged | --no-merged | --contains) [<commit>]] [<pattern>…] + [(--merged | --no-merged | --contains) [<commit>]] [<pattern>…] git branch [--set-upstream | --track | --no-track] [-l] [-f] <branchname> [<start-point>] git branch (--set-upstream-to=<upstream> | -u <upstream>) [<branchname>] git branch --unset-upstream [<branchname>] @@ -73,7 +73,7 @@DESCRIPTION
--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly branches not merged into -the named commit will be listed. If the <commit> argument is missing it +the named commit will be listed. If the <commit> argument is missing it defaults to HEAD (i.e. the tip of the current branch).
Open an editor and edit the text to explain what the branch is
for, to be used by various other commands (e.g. request-pull).
Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.40.0.html b/external/docs/content/docs/git-branch/2.40.0.html
index 671243e59f..76473d029f 100644
--- a/external/docs/content/docs/git-branch/2.40.0.html
+++ b/external/docs/content/docs/git-branch/2.40.0.html
@@ -48,9 +48,9 @@
git branch [--color[=<when>] | --no-color] [--show-current] [-v [--abbrev=<n> | --no-abbrev]] [--column[=<options>] | --no-column] [--sort=<key>] - [--merged [<commit>]] [--no-merged [<commit>]] - [--contains [<commit>]] [--no-contains [<commit>]] - [--points-at <object>] [--format=<format>] + [--merged [<commit>]] [--no-merged [<commit>]] + [--contains [<commit>]] [--no-contains [<commit>]] + [--points-at <object>] [--format=<format>] [(-r | --remotes) | (-a | --all)] [--list] [<pattern>…] git branch [--track[=(direct|inherit)] | --no-track] [-f] @@ -92,7 +92,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches which don’t contain the specified commit
(HEAD if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.41.0.html b/external/docs/content/docs/git-branch/2.41.0.html
index 5df0fb03d8..f9f3848ea0 100644
--- a/external/docs/content/docs/git-branch/2.41.0.html
+++ b/external/docs/content/docs/git-branch/2.41.0.html
@@ -52,9 +52,9 @@
git branch [--color[=<when>] | --no-color] [--show-current] [-v [--abbrev=<n> | --no-abbrev]] [--column[=<options>] | --no-column] [--sort=<key>] - [--merged [<commit>]] [--no-merged [<commit>]] - [--contains [<commit>]] [--no-contains [<commit>]] - [--points-at <object>] [--format=<format>] + [--merged [<commit>]] [--no-merged [<commit>]] + [--contains [<commit>]] [--no-contains [<commit>]] + [--points-at <object>] [--format=<format>] [(-r | --remotes) | (-a | --all)] [--list] [<pattern>…] git branch [--track[=(direct|inherit)] | --no-track] [-f] @@ -96,7 +96,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches which don’t contain the specified commit
(HEAD if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.43.0.html b/external/docs/content/docs/git-branch/2.43.0.html
index 50f04c0799..c4ade7db21 100644
--- a/external/docs/content/docs/git-branch/2.43.0.html
+++ b/external/docs/content/docs/git-branch/2.43.0.html
@@ -51,9 +51,9 @@
git branch [--color[=<when>] | --no-color] [--show-current] [-v [--abbrev=<n> | --no-abbrev]] [--column[=<options>] | --no-column] [--sort=<key>] - [--merged [<commit>]] [--no-merged [<commit>]] - [--contains [<commit>]] [--no-contains [<commit>]] - [--points-at <object>] [--format=<format>] + [--merged [<commit>]] [--no-merged [<commit>]] + [--contains [<commit>]] [--no-contains [<commit>]] + [--points-at <object>] [--format=<format>] [(-r | --remotes) | (-a | --all)] [--list] [<pattern>…] git branch [--track[=(direct|inherit)] | --no-track] [-f] @@ -95,7 +95,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches which don’t contain the specified commit
(HEAD if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.44.0.html b/external/docs/content/docs/git-branch/2.44.0.html
index 91df5d7102..02088b3f27 100644
--- a/external/docs/content/docs/git-branch/2.44.0.html
+++ b/external/docs/content/docs/git-branch/2.44.0.html
@@ -67,9 +67,9 @@
git branch [--color[=<when>] | --no-color] [--show-current] [-v [--abbrev=<n> | --no-abbrev]] [--column[=<options>] | --no-column] [--sort=<key>] - [--merged [<commit>]] [--no-merged [<commit>]] - [--contains [<commit>]] [--no-contains [<commit>]] - [--points-at <object>] [--format=<format>] + [--merged [<commit>]] [--no-merged [<commit>]] + [--contains [<commit>]] [--no-contains [<commit>]] + [--points-at <object>] [--format=<format>] [(-r | --remotes) | (-a | --all)] [--list] [<pattern>…] git branch [--track[=(direct|inherit)] | --no-track] [-f] @@ -111,7 +111,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches which don’t contain the specified commit
(HEAD if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.50.0.html b/external/docs/content/docs/git-branch/2.50.0.html
index bb3fb7fb0e..353871ef2e 100644
--- a/external/docs/content/docs/git-branch/2.50.0.html
+++ b/external/docs/content/docs/git-branch/2.50.0.html
@@ -45,9 +45,9 @@
gitbranch[--color[=<when>] |--no-color] [--show-current] [-v[--abbrev=<n> |--no-abbrev]] [--column[=<options>] |--no-column] [--sort=<key>] - [--merged[<commit>]] [--no-merged[<commit>]] - [--contains[<commit>]] [--no-contains[<commit>]] - [--points-at<object>] [--format=<format>] + [--merged[<commit>]] [--no-merged[<commit>]] + [--contains[<commit>]] [--no-contains[<commit>]] + [--points-at<object>] [--format=<format>] [(-r|--remotes) | (-a|--all)] [--list] [<pattern>…]gitbranch[--track[=(direct|inherit)] |--no-track] [-f] @@ -89,7 +89,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
---contains [<commit>] --contains [<commit>] Only list branches which contain <commit> (HEAD
+
Only list branches which contain <commit> (HEAD
if not specified). Implies --list.
--no-contains [<commit>] --no-contains [<commit>] Only list branches which don’t contain <commit> +
Only list branches which don’t contain <commit>
(HEAD if not specified). Implies --list.
--merged [<commit>] --merged [<commit>] Only list branches whose tips are reachable from
-<commit> (HEAD if not specified). Implies --list.
HEAD if not specified). Implies --list.
--no-merged [<commit>] --no-merged [<commit>] Only list branches whose tips are not reachable from
-<commit> (HEAD if not specified). Implies --list.
HEAD if not specified). Implies --list.
--points-at <object> --points-at <object> Only list branches of <object>.
+Only list branches of <object>.
--format <format> --contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.51.0.html b/external/docs/content/docs/git-branch/2.51.0.html
index 5847175230..497ad43c96 100644
--- a/external/docs/content/docs/git-branch/2.51.0.html
+++ b/external/docs/content/docs/git-branch/2.51.0.html
@@ -44,9 +44,9 @@
gitbranch[--color[=<when>] |--no-color] [--show-current] [-v[--abbrev=<n> |--no-abbrev]] [--column[=<options>] |--no-column] [--sort=<key>] - [--merged[<commit>]] [--no-merged[<commit>]] - [--contains[<commit>]] [--no-contains[<commit>]] - [--points-at<object>] [--format=<format>] + [--merged[<commit>]] [--no-merged[<commit>]] + [--contains[<commit>]] [--no-contains[<commit>]] + [--points-at<object>] [--format=<format>] [(-r|--remotes) | (-a|--all)] [--list] [<pattern>…]gitbranch[--track[=(direct|inherit)] |--no-track] [-f] @@ -88,7 +88,7 @@DESCRIPTION
--no-containsinverts it. With--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly -branches not merged into the named commit will be listed. If the <commit> +branches not merged into the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
--contains [<commit>] --contains [<commit>] Only list branches which contain <commit> (HEAD
+
Only list branches which contain <commit> (HEAD
if not specified). Implies --list.
--no-contains [<commit>] --no-contains [<commit>] Only list branches which don’t contain <commit> +
Only list branches which don’t contain <commit>
(HEAD if not specified). Implies --list.
--merged [<commit>] --merged [<commit>] Only list branches whose tips are reachable from
-<commit> (HEAD if not specified). Implies --list.
HEAD if not specified). Implies --list.
--no-merged [<commit>] --no-merged [<commit>] Only list branches whose tips are not reachable from
-<commit> (HEAD if not specified). Implies --list.
HEAD if not specified). Implies --list.
--points-at <object> --points-at <object> Only list branches of <object>.
+Only list branches of <object>.
--format <format> --contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
-contain the specified <commit>.
--no-contains <commit> is the inverse of that, i.e. branches that don’t
+contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.6.7.html b/external/docs/content/docs/git-branch/2.6.7.html
index c94e5229eb..a7eac4e287 100644
--- a/external/docs/content/docs/git-branch/2.6.7.html
+++ b/external/docs/content/docs/git-branch/2.6.7.html
@@ -42,7 +42,7 @@
git branch [--color[=<when>] | --no-color] [-r | -a] [--list] [-v [--abbrev=<length> | --no-abbrev]] [--column[=<options>] | --no-column] - [(--merged | --no-merged | --contains) [<commit>]] [<pattern>…] + [(--merged | --no-merged | --contains) [<commit>]] [<pattern>…] git branch [--set-upstream | --track | --no-track] [-l] [-f] <branchname> [<start-point>] git branch (--set-upstream-to=<upstream> | -u <upstream>) [<branchname>] git branch --unset-upstream [<branchname>] @@ -72,7 +72,7 @@DESCRIPTION
--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly branches not merged into -the named commit will be listed. If the <commit> argument is missing it +the named commit will be listed. If the <commit> argument is missing it defaults to HEAD (i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.7.6.html b/external/docs/content/docs/git-branch/2.7.6.html
index 5f3f122050..eb04161841 100644
--- a/external/docs/content/docs/git-branch/2.7.6.html
+++ b/external/docs/content/docs/git-branch/2.7.6.html
@@ -43,8 +43,8 @@
git branch [--color[=<when>] | --no-color] [-r | -a] [--list] [-v [--abbrev=<length> | --no-abbrev]] [--column[=<options>] | --no-column] - [(--merged | --no-merged | --contains) [<commit>]] [--sort=<key>] - [--points-at <object>] [<pattern>…] + [(--merged | --no-merged | --contains) [<commit>]] [--sort=<key>] + [--points-at <object>] [<pattern>…] git branch [--set-upstream | --track | --no-track] [-l] [-f] <branchname> [<start-point>] git branch (--set-upstream-to=<upstream> | -u <upstream>) [<branchname>] git branch --unset-upstream [<branchname>] @@ -74,7 +74,7 @@DESCRIPTION
--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly branches not merged into -the named commit will be listed. If the <commit> argument is missing it +the named commit will be listed. If the <commit> argument is missing it defaults to HEAD (i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/2.9.5.html b/external/docs/content/docs/git-branch/2.9.5.html
index 26acb781ec..c3cb86457c 100644
--- a/external/docs/content/docs/git-branch/2.9.5.html
+++ b/external/docs/content/docs/git-branch/2.9.5.html
@@ -44,8 +44,8 @@
git branch [--color[=<when>] | --no-color] [-r | -a] [--list] [-v [--abbrev=<length> | --no-abbrev]] [--column[=<options>] | --no-column] - [(--merged | --no-merged | --contains) [<commit>]] [--sort=<key>] - [--points-at <object>] [<pattern>…] + [(--merged | --no-merged | --contains) [<commit>]] [--sort=<key>] + [--points-at <object>] [<pattern>…] git branch [--set-upstream | --track | --no-track] [-l] [-f] <branchname> [<start-point>] git branch (--set-upstream-to=<upstream> | -u <upstream>) [<branchname>] git branch --unset-upstream [<branchname>] @@ -75,7 +75,7 @@DESCRIPTION
--merged, only branches merged into the named commit (i.e. the branches whose tip commits are reachable from the named commit) will be listed. With--no-mergedonly branches not merged into -the named commit will be listed. If the <commit> argument is missing it +the named commit will be listed. If the <commit> argument is missing it defaults toHEAD(i.e. the tip of the current branch).
request-pull, and merge (if enabled)). Multi-line explanations
may be used.
-Only list branches which contain the specified commit (HEAD
if not specified). Implies --list.
Only list branches whose tips are reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches whose tips are not reachable from the
specified commit (HEAD if not specified). Implies --list.
Only list branches of the given object.
--contains <commit> is used to find all branches which will need
-special attention if <commit> were to be rebased or amended, since those
-branches contain the specified <commit>.
--contains <commit> is used to find all branches which will need
+special attention if <commit> were to be rebased or amended, since those
+branches contain the specified <commit>.
--merged is used to find all branches which can be safely deleted,
diff --git a/external/docs/content/docs/git-branch/fr.html b/external/docs/content/docs/git-branch/fr.html
index 0528cbc23a..2c6e5e5747 100644
--- a/external/docs/content/docs/git-branch/fr.html
+++ b/external/docs/content/docs/git-branch/fr.html
@@ -46,9 +46,9 @@
gitbranch[--color[=<when>] |--no-color] [--show-current] [-v[--abbrev=<n> |--no-abbrev]] [--column[=<options>] |--no-column] [--sort=<clé>] - [--merged[<commit>]] [--no-merged) [<commit>]] - [--contains[<commit>]] [--no-contains[<commit>]] - [--points-at<objet>] [--format=<format>] + [--merged[<commit>]] [--no-merged) [<commit>]] + [--contains[<commit>]] [--no-contains[<commit>]] + [--points-at<objet>] [--format=<format>] [(-r|--remotes) | (-a|--all)] [--list] [<motif>…]gitbranch[--track[=(direct|inherit)] |--no-track] [-f] @@ -75,7 +75,7 @@DESCRIPTION
Notez que lorsque vous fournissez un <motif>,vousdevezutiliser--list; sinon, la commande peut être interprétée comme une création de branche.
Avec --contains, montrer seulement les branches qui contiennent le commit indiqué (en d’autres termes, les branches dont les commits sommets sont des descendants du commit indiqué), avec --no-contains inverser. Avec --merged, seules les branches fusionnées dans le commit indiqué (c’est-à-dire les branches dont les commits sommets sont accessibles depuis le commit indiqué) seront listées. Avec --no-merged, seules les branches non fusionnées dans le commit indiqué seront listées. Si l’argument <commit> est manquant, il prend par défaut la valeur HEAD (c’est-à-dire le sommet de la branche courante).
Avec --contains, montrer seulement les branches qui contiennent le commit indiqué (en d’autres termes, les branches dont les commits sommets sont des descendants du commit indiqué), avec --no-contains inverser. Avec --merged, seules les branches fusionnées dans le commit indiqué (c’est-à-dire les branches dont les commits sommets sont accessibles depuis le commit indiqué) seront listées. Avec --no-merged, seules les branches non fusionnées dans le commit indiqué seront listées. Si l’argument <commit> est manquant, il prend par défaut la valeur HEAD (c’est-à-dire le sommet de la branche courante).
La deuxième forme de la commande crée une nouvelle tête de branche nommée <nom-de-branche> qui pointe vers la HEAD actuelle, ou <point-de-départ> si elle est fournie. Dans un cas particulier, pour le <point-de-départ>, vous pouvez utiliser <rev-a>...<rev-b> comme raccourci pour la base de fusion de <rev-a> et <rev-b> s’il y a exactement une base de fusion. Vous pouvez omettre tout au plus un des <rev-a> et <rev-b>, auquel cas il s’agit par défaut de HEAD.
-f --force Réinitialiser <branche> à <point-de-départ>, même si <branche> existe déjà. Sans -f, git branch refuse de changer une branche existante. En combinaison avec -d (ou --delete), permettre la suppression de la branche indépendamment de son statut de fusion, ou si elle pointe même sur un commit valide. En combinaison avec -m (ou --move), il est possible de renommer la branche même si le nouveau nom de la branche existe déjà, il en va de même pour -c (ou --copy).
Réinitialiser <branche> à <point-de-départ>, même si <branche> existe déjà. Sans -f, git branch refuse de changer une branche existante. En combinaison avec -d (ou --delete), permettre la suppression de la branche indépendamment de son statut de fusion, ou si elle pointe même sur un commit valide. En combinaison avec -m (ou --move), il est possible de renommer la branche même si le nouveau nom de la branche existe déjà, il en va de même pour -c (ou --copy).
Notez que git branch -f <branche> [<point-de-départ>], même avec -f, refuse de modifier une branche existante <branche> qui est extraite dans un autre arbre-de-travail lié au même dépôt.
Notez que git branch -f <branche> [<point-de-départ>], même avec -f, refuse de modifier une branche existante <branche> qui est extraite dans un autre arbre-de-travail lié au même dépôt.
-m Ouvrir un éditeur et éditer le texte pour expliquer à quoi sert la branche, qui sera utilisée par diverses autres commandes (par exemple format-patch, pull-request et merge (si activé)). Des explications sur plusieurs lignes peuvent être utilisées.
--contains [<commit>] --contains [<commit>] N’indiquer que les branches qui contiennent le commit spécifié (HEAD si non spécifié). Implique --list.
--no-contains [<commit>] --no-contains [<commit>] N’indiquer que les branches qui ne contiennent pas <commit> (HEAD si non spécifié). Implique --list.
N’indiquer que les branches qui ne contiennent pas <commit> (HEAD si non spécifié). Implique --list.
--merged [<commit>] --merged [<commit>] N’indiquer que les branches dont les sommets sont accessibles depuis <commit> (HEAD si non spécifié). Implique --list.
N’indiquer que les branches dont les sommets sont accessibles depuis <commit> (HEAD si non spécifié). Implique --list.
--no-merged [<commit>] --no-merged [<commit>] N’indiquer que les branches dont les sommets ne sont pas accessibles depuis le <commit> (HEAD si non spécifié). Implique --list.
N’indiquer que les branches dont les sommets ne sont pas accessibles depuis le <commit> (HEAD si non spécifié). Implique --list.
--points-at <objet> --points-at <objet> N’indiquer que les branches de <objet>.
+N’indiquer que les branches de <objet>.
--format <format> --contains <commit> est utilisé pour trouver toutes les branches qui devront faire l’objet d’une attention particulière si <commit> devait être rebasé ou modifié, puisque ces branches contiennent le <commit> spécifié.
--contains <commit> est utilisé pour trouver toutes les branches qui devront faire l’objet d’une attention particulière si <commit> devait être rebasé ou modifié, puisque ces branches contiennent le <commit> spécifié.
--no-contains <commit> est l’inverse de cela, c’est-à-dire les branches qui ne contiennent pas le <commit> spécifié.
--no-contains <commit> est l’inverse de cela, c’est-à-dire les branches qui ne contiennent pas le <commit> spécifié.
--merged est utilisé pour trouver toutes les branches qui peuvent être supprimées en toute sécurité, puisque ces branches sont entièrement contenues par HEAD.
git branch [--color[=<quando>] | --no-color] [--show-current] [-v [--abbrev=<n> | --no-abbrev]] [--column[=<opções>] | --no-column] [--sort=<chaves>] - [--merged [<commit>]] [--no-merged [<commit>]] - [--contains [<commit>]] [--no-contains [<commit>]] + [--merged [<commit>]] [--no-merged [<commit>]] + [--contains [<commit>]] [--no-contains [<commit>]] [--points-at <objeto>] [--format=<formato>] [(-r | --remotes) | (-a | --all)] [--list] [<padrão>…] @@ -73,7 +73,7 @@DESCRIÇÃO
Note que ao fornecer um <padrão> você deve utilizar--list; caso contrário, o comando pode ser interpretado como uma criação do ramo.
Com --contains, mostra apenas os ramos que contêm o commit indicado (em outras palavras, os ramos cujos commits do cume são descendentes do commit nomeado), a opção --no-contains inverte isso. Com a opção --merged, apenas as ramificações mescladas no commit indicado (ou seja, as ramificações cujos commits principais são acessíveis a partir do commit indicado) serão listados. Com a opção --no-merged, apenas as ramificações não mescladas no commit indicado serão listados. Se o argumento <commit> estiver ausente, a predefinição será HEAD (ou seja, o cume do ramo atual).
Com --contains, mostra apenas os ramos que contêm o commit indicado (em outras palavras, os ramos cujos commits do cume são descendentes do commit nomeado), a opção --no-contains inverte isso. Com a opção --merged, apenas as ramificações mescladas no commit indicado (ou seja, as ramificações cujos commits principais são acessíveis a partir do commit indicado) serão listados. Com a opção --no-merged, apenas as ramificações não mescladas no commit indicado serão listados. Se o argumento <commit> estiver ausente, a predefinição será HEAD (ou seja, o cume do ramo atual).
O segundo formulário do comando cria um novo cabeçalho do ramo informado <nome-do-ramo> (nome do ramo0), que aponta para o HEAD atual, ou o <ponto-de-partida> caso seja utilizado. Como um caso especial, para o <ponto-de-partida>, utilize "A...B" como um atalho para a base da mesclagem de A e B caso sejam exatamente uma base para ser mesclada. Você pode deixar de fora no máximo um de A e B, caso onde a predefinição retorna para HEAD.
Abra um editor e edite o texto para explicar para que serve a ramificação, para ser utilizado por outros comandos (format-patch, request-pull e merge por exemplo (se ativado)). Podem ser utilizadas as explicações em mais de uma linha.
Listar apenas as ramificações que contenham o commit informado (HEAD, caso nenhum seja informado). Implica no uso da opção --list.
Liste apenas as ramificações que não contenha o commit informado (HEAD, caso nenhum seja informado). Implica no uso da opção --list.
Liste apenas as ramificações cujas dicas são acessíveis a partir do commit informado (HEAD, caso nenhum seja informado). Implica no uso da opção --list.
Liste apenas as ramificações cujas dicas não possam ser acessadas a partir do commit informado (HEAD, caso nenhum seja informado). Implica no uso da opção --list.
--contains <commit> é utilizado para encontrar todas as ramificações que precisarão de atenção especial caso <commit> precise de um novo "rebase" ou corrigido, uma vez que essas ramificações contêm o <commit> informato.
--contains <commit> é utilizado para encontrar todas as ramificações que precisarão de atenção especial caso <commit> precise de um novo "rebase" ou corrigido, uma vez que essas ramificações contêm o <commit> informato.
--no-contains <commit> é o inverso, isto é, as ramificações que não contêm o <commit> informado.
--no-contains <commit> é o inverso, isto é, as ramificações que não contêm o <commit> informado.
--merged é utilizado para encontrar todas as ramificações que podem ser excluídas com segurança, uma vez que essas ramificações são totalmente contidas pelo HEAD.
Сортировать по заданному ключу. Добавьте префикс -, чтобы отсортировать в порядке убывания значения. Вы можете использовать параметр --sort=<ключ> несколько раз, в таком случае последний ключ становится основным. Поддерживаются те же ключи, что и в git for-each-ref. Порядок сортировки по умолчанию соответствует значению переменной конфигурации branch.sort, если она задана, или сортировке по полному имени ссылки (включая префикс refs/...). Это означает, что сначала в списке будут идти отсоединённый указатель HEAD (если есть), затем локальные ветки и наконец отслеживаемые внешние ветки. См. git-config[1].
Перечислить только ветки данного объекта.
打开一个编辑器，编辑文本，解释该分支的用途，以便被其他各种命令（如`format-patch`、request-pull`和`merge（如果启用））使用。可以使用多行解释。
只列出包含指定提交的分支（如果没有指定则为HEAD）。意味着 --list。
只列出不包含指定提交的分支（如果不指定则为HEAD）。意味着 --list。
只列出从指定的提交（如果没有指定，则为HEAD）可以到达的分支的提示。意味着 --list。
只列出从指定的提交（如果没有指定，则为HEAD）中无法到达的分支。意味着 --list。
根据给定的键进行排序。前缀"-"表示按照数值的降序排序。你可以多次使用 --sort=<键> 选项，在这种情况下，最后一个键成为主键。支持的键与 git for-each-ref 中的键相同。排序顺序默认为 branch.sort 变量的配置值（如果存在），或者基于完整的引用名（包括 refs/... 前缀）进行排序。这将首先列出分离的 HEAD（如果存在），然后是本地分支，最后是远程跟踪分支。参见 git-config[1]。
只列出给定对象的分支。
Une manière naïve de faire une sauvegarde complète d’un dépôt est d’utiliser quelque chose qui fait comme cp -r <dépôt> <destination>. Cela est découragé puisque le dépôt pourrait être écrit pendant l’opération de copie. À son tour, certains fichiers dans <destination> pourraient être corrompus.
Une manière naïve de faire une sauvegarde complète d’un dépôt est d’utiliser quelque chose qui fait comme cp -r <dépôt> <destination>. Cela est découragé puisque le dépôt pourrait être écrit pendant l’opération de copie. À son tour, certains fichiers dans <destination> pourraient être corrompus.
C’est pourquoi il est recommandé d’utiliser l’outillage Git pour faire des sauvegardes de dépôt, soit avec cette commande soit par exemple avec git-clone[1]. Mais gardez à l’esprit que ces outils ne vous aideront pas à sauvegarder l’état autre que les refs et les commits. En d’autres termes, ils ne vous aideront pas à sauvegarder le contenu de l’index, l’arbre de travail, la remise, la configuration par dépôt, les crochets, etc.
diff --git a/external/docs/content/docs/git-cat-file.html b/external/docs/content/docs/git-cat-file.html index 3539bf15e1..ea143bd19c 100644 --- a/external/docs/content/docs/git-cat-file.html +++ b/external/docs/content/docs/git-cat-file.html @@ -40,8 +40,8 @@git cat-file <type> <object> -git cat-file (-e | -p | -t | -s) <object> +git cat-file <type> <object> +git cat-file (-e | -p | -t | -s) <object> git cat-file (--textconv | --filters) [<rev>:<path|tree-ish> | --path=<path|tree-ish> <rev>] git cat-file (--batch | --batch-check | --batch-command) [--batch-all-objects] @@ -75,7 +75,7 @@OPTIONS
-
- <object>
+- <object>
The name of the object to show. For a more complete list of ways to spell object names, see @@ -84,32 +84,32 @@
OPTIONS
- -t
Instead of the content, show the object type identified by -<object>.
+<object>.- -s
Instead of the content, show the object size identified by -<object>. If used with
--use-mailmapoption, will show +<object>. If used with--use-mailmapoption, will show the size of updated object after replacing idents using the mailmap mechanism.- -e
- -
Exit with zero status if <object> exists and is a valid -object. If <object> is of an invalid format, exit with non-zero +
Exit with zero status if <object> exists and is a valid +object. If <object> is of an invalid format, exit with non-zero status and emit an error on stderr.
- -p
- -
Pretty-print the contents of <object> based on its type.
+Pretty-print the contents of <object> based on its type.
- <type>
- -
Typically this matches the real type of <object> but asking +
Typically this matches the real type of <object> but asking for a type that can trivially be dereferenced from the given -<object> is also permitted. An example is to ask for a -"tree" with <object> being a commit object that contains it, -or to ask for a "blob" with <object> being a tag object that +<object> is also permitted. An example is to ask for a +"tree" with <object> being a commit object that contains it, +or to ask for a "blob" with <object> being a tag object that points at it.
- --[no-]mailmap
@@ -122,7 +122,7 @@OPTIONS
- --textconv
- @@ -130,8 +130,8 @@
Show the content as transformed by a textconv filter. In this case, -<object> has to be of the form <tree-ish>
:<path>, or:<path> in +<object> has to be of the form <tree-ish>:<path>, or:<path> in order to apply the filter to the content recorded in the index at <path>.OPTIONS
Show the content as converted by the filters configured in the current working tree for the given <path> (i.e. smudge filters, -end-of-line conversion, etc). In this case, <object> has to be of -the form <tree-ish>
+end-of-line conversion, etc). In this case, <object> has to be of +the form <tree-ish>:<path>, or:<path>.:<path>, or:<path>.- --filter=<filter-spec>
- --no-filter
@@ -247,14 +247,14 @@OPTIONS
@@ -521,7 +521,7 @@-
- contents <object>
+- contents <object>
- -
-Print object contents for object reference <object>. This corresponds to +
Print object contents for object reference <object>. This corresponds to the output of
--batch.- info <object>
+- info <object>
- -
Print object info for object reference <object>. This corresponds to the +
Print object info for object reference <object>. This corresponds to the output of
--batch-check.- flush
@@ -408,16 +408,16 @@OUTPUT
If
-tis specified, one of the <type>.-If
+-sis specified, the size of the <object> in bytes.If
-sis specified, the size of the <object> in bytes.-If
+-eis specified, no output, unless the <object> is malformed.If
-eis specified, no output, unless the <object> is malformed.-If
+-pis specified, the contents of <object> are pretty-printed.If
-pis specified, the contents of <object> are pretty-printed.-If <type> is specified, the raw (though uncompressed) contents of the <object> +
If <type> is specified, the raw (though uncompressed) contents of the <object> will be returned.
BATCH OUTPUT<
-<object> SP missing LF+<object> SP missing LF-<object> SP excluded LF+<object> SP excluded LF-<object> SP ambiguous LF+<object> SP ambiguous LF-<object> SP missing LF+<object> SP missing LF@@ -582,7 +582,7 @@BATCH OUTPUT<
dangling SP <size> LF -<object> LF+<object> LF@@ -592,7 +592,7 @@BATCH OUTPUT<
loop SP <size> LF -<object> LF+<object> LF@@ -602,7 +602,7 @@diff --git a/external/docs/content/docs/git-cat-file/2.11.4.html b/external/docs/content/docs/git-cat-file/2.11.4.html index 1ff74cf8a3..f716ed29c2 100644 --- a/external/docs/content/docs/git-cat-file/2.11.4.html +++ b/external/docs/content/docs/git-cat-file/2.11.4.html @@ -41,7 +41,7 @@BATCH OUTPUT<
notdir SP <size> LF -<object> LF+<object> LFdiff --git a/external/docs/content/docs/git-cat-file/2.0.5.html b/external/docs/content/docs/git-cat-file/2.0.5.html index e742554e12..1758f4cedc 100644 --- a/external/docs/content/docs/git-cat-file/2.0.5.html +++ b/external/docs/content/docs/git-cat-file/2.0.5.html @@ -43,7 +43,7 @@NAME
SYNOPSIS
@@ -68,7 +68,7 @@-git cat-file (-t | -s | -e | -p | <type> | --textconv ) <object> +git cat-file (-t | -s | -e | -p | <type> | --textconv ) <object> git cat-file (--batch | --batch-check) < <list-of-objects>OPTIONS
@@ -231,7 +231,7 @@-
- <object>
+- <object>
The name of the object to show. For a more complete list of ways to spell object names, see @@ -77,35 +77,35 @@
OPTIONS
- -t
Instead of the content, show the object type identified by -<object>.
+<object>.- -s
Instead of the content, show the object size identified by -<object>.
+<object>.- -e
- -
Suppress all output; instead exit with zero status if <object> +
Suppress all output; instead exit with zero status if <object> exists and is a valid object.
- -p
- -
Pretty-print the contents of <object> based on its type.
+Pretty-print the contents of <object> based on its type.
- <type>
- -
Typically this matches the real type of <object> but asking +
Typically this matches the real type of <object> but asking for a type that can trivially be dereferenced from the given -<object> is also permitted. An example is to ask for a -"tree" with <object> being a commit object that contains it, -or to ask for a "blob" with <object> being a tag object that +<object> is also permitted. An example is to ask for a +"tree" with <object> being a commit object that contains it, +or to ask for a "blob" with <object> being a tag object that points at it.
- --textconv
Show the content as transformed by a textconv filter. In this case, -<object> has be of the form <tree-ish>:<path>, or :<path> in order +<object> has be of the form <tree-ish>:<path>, or :<path> in order to apply the filter to the content recorded in the index at <path>.
- --batch
@@ -133,16 +133,16 @@OUTPUT
If -t is specified, one of the <type>.
-If -s is specified, the size of the <object> in bytes.
+If -s is specified, the size of the <object> in bytes.
If -e is specified, no output.
-If -p is specified, the contents of <object> are pretty-printed.
+If -p is specified, the contents of <object> are pretty-printed.
-If <type> is specified, the raw (though uncompressed) contents of the <object> +
If <type> is specified, the raw (though uncompressed) contents of the <object> will be returned.
BATCH OUTPUT<
-<object> SP missing LF+<object> SP missing LFNAME
SYNOPSIS
@@ -70,7 +70,7 @@-git cat-file (-t [--allow-unknown-type]| -s [--allow-unknown-type]| -e | -p | <type> | --textconv | --filters ) [--path=<path>] <object> +git cat-file (-t [--allow-unknown-type]| -s [--allow-unknown-type]| -e | -p | <type> | --textconv | --filters ) [--path=<path>] <object> git cat-file (--batch | --batch-check) [ --textconv | --filters ] [--follow-symlinks]OPTIONS
@@ -357,7 +357,7 @@-
- <object>
+- <object>
The name of the object to show. For a more complete list of ways to spell object names, see @@ -79,35 +79,35 @@
OPTIONS
- -t
Instead of the content, show the object type identified by -<object>.
+<object>.- -s
Instead of the content, show the object size identified by -<object>.
+<object>.- -e
- -
Suppress all output; instead exit with zero status if <object> +
Suppress all output; instead exit with zero status if <object> exists and is a valid object.
- -p
- -
Pretty-print the contents of <object> based on its type.
+Pretty-print the contents of <object> based on its type.
- <type>
- -
Typically this matches the real type of <object> but asking +
Typically this matches the real type of <object> but asking for a type that can trivially be dereferenced from the given -<object> is also permitted. An example is to ask for a -"tree" with <object> being a commit object that contains it, -or to ask for a "blob" with <object> being a tag object that +<object> is also permitted. An example is to ask for a +"tree" with <object> being a commit object that contains it, +or to ask for a "blob" with <object> being a tag object that points at it.
- --textconv
- @@ -115,8 +115,8 @@
Show the content as transformed by a textconv filter. In this case, -<object> has to be of the form <tree-ish>:<path>, or :<path> in +<object> has to be of the form <tree-ish>:<path>, or :<path> in order to apply the filter to the content recorded in the index at <path>.
OPTIONS
Show the content as converted by the filters configured in the current working tree for the given <path> (i.e. smudge filters, -end-of-line conversion, etc). In this case, <object> has to be of -the form <tree-ish>:<path>, or :<path>.
+end-of-line conversion, etc). In this case, <object> has to be of +the form <tree-ish>:<path>, or :<path>.- --path=<path>
- @@ -259,16 +259,16 @@
OUTPUT
If
-tis specified, one of the <type>.-If
+-sis specified, the size of the <object> in bytes.If
-sis specified, the size of the <object> in bytes.If
-eis specified, no output.-If
+-pis specified, the contents of <object> are pretty-printed.If
-pis specified, the contents of <object> are pretty-printed.-If <type> is specified, the raw (though uncompressed) contents of the <object> +
If <type> is specified, the raw (though uncompressed) contents of the <object> will be returned.
BATCH OUTPUT<
-<object> SP missing LF+<object> SP missing LF-<object> SP missing LF+<object> SP missing LF@@ -391,7 +391,7 @@BATCH OUTPUT<
dangling SP <size> LF -<object> LF+<object> LF@@ -401,7 +401,7 @@BATCH OUTPUT<
loop SP <size> LF -<object> LF+<object> LF@@ -411,7 +411,7 @@BATCH OUTPUT<
notdir SP <size> LF -<object> LF+<object> LFdiff --git a/external/docs/content/docs/git-cat-file/2.14.6.html b/external/docs/content/docs/git-cat-file/2.14.6.html index 7bdf2dac52..82fd12c937 100644 --- a/external/docs/content/docs/git-cat-file/2.14.6.html +++ b/external/docs/content/docs/git-cat-file/2.14.6.html @@ -40,7 +40,7 @@NAME
SYNOPSIS
@@ -69,7 +69,7 @@-git cat-file (-t [--allow-unknown-type]| -s [--allow-unknown-type]| -e | -p | <type> | --textconv | --filters ) [--path=<path>] <object> +git cat-file (-t [--allow-unknown-type]| -s [--allow-unknown-type]| -e | -p | <type> | --textconv | --filters ) [--path=<path>] <object> git cat-file (--batch | --batch-check) [ --textconv | --filters ] [--follow-symlinks]OPTIONS
@@ -356,7 +356,7 @@-
- <object>
+- <object>
The name of the object to show. For a more complete list of ways to spell object names, see @@ -78,35 +78,35 @@
OPTIONS
- -t
Instead of the content, show the object type identified by -<object>.
+<object>.- -s
Instead of the content, show the object size identified by -<object>.
+<object>.- -e
- -
Suppress all output; instead exit with zero status if <object> +
Suppress all output; instead exit with zero status if <object> exists and is a valid object.
- -p
- -
Pretty-print the contents of <object> based on its type.
+Pretty-print the contents of <object> based on its type.
- <type>
- -
Typically this matches the real type of <object> but asking +
Typically this matches the real type of <object> but asking for a type that can trivially be dereferenced from the given -<object> is also permitted. An example is to ask for a -"tree" with <object> being a commit object that contains it, -or to ask for a "blob" with <object> being a tag object that +<object> is also permitted. An example is to ask for a +"tree" with <object> being a commit object that contains it, +or to ask for a "blob" with <object> being a tag object that points at it.
- --textconv
- @@ -114,8 +114,8 @@
Show the content as transformed by a textconv filter. In this case, -<object> has to be of the form <tree-ish>:<path>, or :<path> in +<object> has to be of the form <tree-ish>:<path>, or :<path> in order to apply the filter to the content recorded in the index at <path>.
OPTIONS
Show the content as converted by the filters configured in the current working tree for the given <path> (i.e. smudge filters, -end-of-line conversion, etc). In this case, <object> has to be of -the form <tree-ish>:<path>, or :<path>.
+end-of-line conversion, etc). In this case, <object> has to be of +the form <tree-ish>:<path>, or :<path>.- --path=<path>
- @@ -258,16 +258,16 @@
OUTPUT
If
-tis specified, one of the <type>.-If
+-sis specified, the size of the <object> in bytes.If
-sis specified, the size of the <object> in bytes.If
-eis specified, no output.-If
+-pis specified, the contents of <object> are pretty-printed.If
-pis specified, the contents of <object> are pretty-printed.-If <type> is specified, the raw (though uncompressed) contents of the <object> +
If <type> is specified, the raw (though uncompressed) contents of the <object> will be returned.
BATCH OUTPUT<
-<object> SP missing LF+<object> SP missing LF-<object> SP missing LF+<object> SP missing LF@@ -390,7 +390,7 @@BATCH OUTPUT<
dangling SP <size> LF -<object> LF+<object> LF@@ -400,7 +400,7 @@BATCH OUTPUT<
loop SP <size> LF -<object> LF+<object> LF@@ -410,7 +410,7 @@BATCH OUTPUT<
notdir SP <size> LF -<object> LF+<object> LFdiff --git a/external/docs/content/docs/git-cat-file/2.16.6.html b/external/docs/content/docs/git-cat-file/2.16.6.html index 3319a989f5..e433974ae8 100644 --- a/external/docs/content/docs/git-cat-file/2.16.6.html +++ b/external/docs/content/docs/git-cat-file/2.16.6.html @@ -52,7 +52,7 @@NAME
SYNOPSIS
@@ -81,7 +81,7 @@-git cat-file (-t [--allow-unknown-type]| -s [--allow-unknown-type]| -e | -p | <type> | --textconv | --filters ) [--path=<path>] <object> +git cat-file (-t [--allow-unknown-type]| -s [--allow-unknown-type]| -e | -p | <type> | --textconv | --filters ) [--path=<path>] <object> git cat-file (--batch | --batch-check) [ --textconv | --filters ] [--follow-symlinks]OPTIONS
@@ -369,7 +369,7 @@-
- <object>
+- <object>
The name of the object to show. For a more complete list of ways to spell object names, see @@ -90,36 +90,36 @@
OPTIONS
- -t
Instead of the content, show the object type identified by -<object>.
+<object>.- -s
Instead of the content, show the object size identified by -<object>.
+<object>.- -e
- -
Exit with zero status if <object> exists and is a valid -object. If <object> is of an invalid format exit with non-zero and +
Exit with zero status if <object> exists and is a valid +object. If <object> is of an invalid format exit with non-zero and emits an error on stderr.
- -p
- -
Pretty-print the contents of <object> based on its type.
+Pretty-print the contents of <object> based on its type.
- <type>
- -
Typically this matches the real type of <object> but asking +
Typically this matches the real type of <object> but asking for a type that can trivially be dereferenced from the given -<object> is also permitted. An example is to ask for a -"tree" with <object> being a commit object that contains it, -or to ask for a "blob" with <object> being a tag object that +<object> is also permitted. An example is to ask for a +"tree" with <object> being a commit object that contains it, +or to ask for a "blob" with <object> being a tag object that points at it.
- --textconv
- @@ -127,8 +127,8 @@
Show the content as transformed by a textconv filter. In this case, -<object> has to be of the form <tree-ish>:<path>, or :<path> in +<object> has to be of the form <tree-ish>:<path>, or :<path> in order to apply the filter to the content recorded in the index at <path>.
OPTIONS
Show the content as converted by the filters configured in the current working tree for the given <path> (i.e. smudge filters, -end-of-line conversion, etc). In this case, <object> has to be of -the form <tree-ish>:<path>, or :<path>.
+end-of-line conversion, etc). In this case, <object> has to be of +the form <tree-ish>:<path>, or :<path>.- --path=<path>
- @@ -271,16 +271,16 @@
OUTPUT
If
-tis specified, one of the <type>.-If
+-sis specified, the size of the <object> in bytes.If
-sis specified, the size of the <object> in bytes.-If
+-eis specified, no output, unless the <object> is malformed.If
-eis specified, no output, unless the <object> is malformed.-If
+-pis specified, the contents of <object> are pretty-printed.If
-pis specified, the contents of <object> are pretty-printed.-If <type> is specified, the raw (though uncompressed) contents of the <object> +
If <type> is specified, the raw (though uncompressed) contents of the <object> will be returned.
BATCH OUTPUT<
-<object> SP missing LF+<object> SP missing LF-<object> SP missing LF+<object> SP missing LF@@ -403,7 +403,7 @@BATCH OUTPUT<
dangling SP <size> LF -<object> LF+<object> LF@@ -413,7 +413,7 @@BATCH OUTPUT<
loop SP <size> LF -<object> LF+<object> LF@@ -423,7 +423,7 @@BATCH OUTPUT<
notdir SP <size> LF -<object> LF+<object> LFdiff --git a/external/docs/content/docs/git-cat-file/2.19.0.html b/external/docs/content/docs/git-cat-file/2.19.0.html index 0f8d0f52a1..670956cc09 100644 --- a/external/docs/content/docs/git-cat-file/2.19.0.html +++ b/external/docs/content/docs/git-cat-file/2.19.0.html @@ -51,7 +51,7 @@NAME
SYNOPSIS
@@ -80,7 +80,7 @@-git cat-file (-t [--allow-unknown-type]| -s [--allow-unknown-type]| -e | -p | <type> | --textconv | --filters ) [--path=<path>] <object> +git cat-file (-t [--allow-unknown-type]| -s [--allow-unknown-type]| -e | -p | <type> | --textconv | --filters ) [--path=<path>] <object> git cat-file (--batch | --batch-check) [ --textconv | --filters ] [--follow-symlinks]OPTIONS
@@ -379,7 +379,7 @@-
- <object>
+- <object>
The name of the object to show. For a more complete list of ways to spell object names, see @@ -89,36 +89,36 @@
OPTIONS
- -t
Instead of the content, show the object type identified by -<object>.
+<object>.- -s
Instead of the content, show the object size identified by -<object>.
+<object>.- -e
- -
Exit with zero status if <object> exists and is a valid -object. If <object> is of an invalid format exit with non-zero and +
Exit with zero status if <object> exists and is a valid +object. If <object> is of an invalid format exit with non-zero and emits an error on stderr.
- -p
- -
Pretty-print the contents of <object> based on its type.
+Pretty-print the contents of <object> based on its type.
- <type>
- -
Typically this matches the real type of <object> but asking +
Typically this matches the real type of <object> but asking for a type that can trivially be dereferenced from the given -<object> is also permitted. An example is to ask for a -"tree" with <object> being a commit object that contains it, -or to ask for a "blob" with <object> being a tag object that +<object> is also permitted. An example is to ask for a +"tree" with <object> being a commit object that contains it, +or to ask for a "blob" with <object> being a tag object that points at it.
- --textconv
- @@ -126,8 +126,8 @@
Show the content as transformed by a textconv filter. In this case, -<object> has to be of the form <tree-ish>:<path>, or :<path> in +<object> has to be of the form <tree-ish>:<path>, or :<path> in order to apply the filter to the content recorded in the index at <path>.
OPTIONS
Show the content as converted by the filters configured in the current working tree for the given <path> (i.e. smudge filters, -end-of-line conversion, etc). In this case, <object> has to be of -the form <tree-ish>:<path>, or :<path>.
+end-of-line conversion, etc). In this case, <object> has to be of +the form <tree-ish>:<path>, or :<path>.- --path=<path>
- @@ -281,16 +281,16 @@
OUTPUT
If
-tis specified, one of the <type>.-If
+-sis specified, the size of the <object> in bytes.If
-sis specified, the size of the <object> in bytes.-If
+-eis specified, no output, unless the <object> is malformed.If
-eis specified, no output, unless the <object> is malformed.-If
+-pis specified, the contents of <object> are pretty-printed.If
-pis specified, the contents of <object> are pretty-printed.-If <type> is specified, the raw (though uncompressed) contents of the <object> +
If <type> is specified, the raw (though uncompressed) contents of the <object> will be returned.
BATCH OUTPUT<
-<object> SP missing LF+<object> SP missing LF-<object> SP missing LF+<object> SP missing LF@@ -413,7 +413,7 @@BATCH OUTPUT<
dangling SP <size> LF -<object> LF+<object> LF@@ -423,7 +423,7 @@BATCH OUTPUT<
loop SP <size> LF -<object> LF+<object> LF@@ -433,7 +433,7 @@BATCH OUTPUT<
notdir SP <size> LF -<object> LF+<object> LFdiff --git a/external/docs/content/docs/git-cat-file/2.21.0.html b/external/docs/content/docs/git-cat-file/2.21.0.html index 6be3d089a1..621a8426ab 100644 --- a/external/docs/content/docs/git-cat-file/2.21.0.html +++ b/external/docs/content/docs/git-cat-file/2.21.0.html @@ -71,7 +71,7 @@NAME
SYNOPSIS
@@ -100,7 +100,7 @@-git cat-file (-t [--allow-unknown-type]| -s [--allow-unknown-type]| -e | -p | <type> | --textconv | --filters ) [--path=<path>] <object> +git cat-file (-t [--allow-unknown-type]| -s [--allow-unknown-type]| -e | -p | <type> | --textconv | --filters ) [--path=<path>] <object> git cat-file (--batch | --batch-check) [ --textconv | --filters ] [--follow-symlinks]OPTIONS
@@ -399,7 +399,7 @@-
- <object>
+- <object>
The name of the object to show. For a more complete list of ways to spell object names, see @@ -109,36 +109,36 @@
OPTIONS
- -t
Instead of the content, show the object type identified by -<object>.
+<object>.- -s
Instead of the content, show the object size identified by -<object>.
+<object>.- -e
- -
Exit with zero status if <object> exists and is a valid -object. If <object> is of an invalid format exit with non-zero and +
Exit with zero status if <object> exists and is a valid +object. If <object> is of an invalid format exit with non-zero and emits an error on stderr.
- -p
- -
Pretty-print the contents of <object> based on its type.
+Pretty-print the contents of <object> based on its type.
- <type>
- -
Typically this matches the real type of <object> but asking +
Typically this matches the real type of <object> but asking for a type that can trivially be dereferenced from the given -<object> is also permitted. An example is to ask for a -"tree" with <object> being a commit object that contains it, -or to ask for a "blob" with <object> being a tag object that +<object> is also permitted. An example is to ask for a +"tree" with <object> being a commit object that contains it, +or to ask for a "blob" with <object> being a tag object that points at it.
- --textconv
- @@ -146,8 +146,8 @@
Show the content as transformed by a textconv filter. In this case, -<object> has to be of the form <tree-ish>:<path>, or :<path> in +<object> has to be of the form <tree-ish>:<path>, or :<path> in order to apply the filter to the content recorded in the index at <path>.
OPTIONS
Show the content as converted by the filters configured in the current working tree for the given <path> (i.e. smudge filters, -end-of-line conversion, etc). In this case, <object> has to be of -the form <tree-ish>:<path>, or :<path>.
+end-of-line conversion, etc). In this case, <object> has to be of +the form <tree-ish>:<path>, or :<path>.- --path=<path>
- @@ -301,16 +301,16 @@
OUTPUT
If
-tis specified, one of the <type>.-If
+-sis specified, the size of the <object> in bytes.If
-sis specified, the size of the <object> in bytes.-If
+-eis specified, no output, unless the <object> is malformed.If
-eis specified, no output, unless the <object> is malformed.-If
+-pis specified, the contents of <object> are pretty-printed.If
-pis specified, the contents of <object> are pretty-printed.-If <type> is specified, the raw (though uncompressed) contents of the <object> +
If <type> is specified, the raw (though uncompressed) contents of the <object> will be returned.
BATCH OUTPUT<
-<object> SP missing LF+<object> SP missing LF-<object> SP ambiguous LF+<object> SP ambiguous LF-<object> SP missing LF+<object> SP missing LF@@ -441,7 +441,7 @@BATCH OUTPUT<
dangling SP <size> LF -<object> LF+<object> LF@@ -451,7 +451,7 @@BATCH OUTPUT<
loop SP <size> LF -<object> LF+<object> LF@@ -461,7 +461,7 @@BATCH OUTPUT<
notdir SP <size> LF -<object> LF+<object> LFdiff --git a/external/docs/content/docs/git-cat-file/2.28.0.html b/external/docs/content/docs/git-cat-file/2.28.0.html index 79c9645d49..3b141e010b 100644 --- a/external/docs/content/docs/git-cat-file/2.28.0.html +++ b/external/docs/content/docs/git-cat-file/2.28.0.html @@ -63,7 +63,7 @@NAME
SYNOPSIS
@@ -92,7 +92,7 @@-git cat-file (-t [--allow-unknown-type]| -s [--allow-unknown-type]| -e | -p | <type> | --textconv | --filters ) [--path=<path>] <object> +git cat-file (-t [--allow-unknown-type]| -s [--allow-unknown-type]| -e | -p | <type> | --textconv | --filters ) [--path=<path>] <object> git cat-file (--batch[=<format>] | --batch-check[=<format>]) [ --textconv | --filters ] [--follow-symlinks]OPTIONS
@@ -391,7 +391,7 @@-
- <object>
+- <object>
The name of the object to show. For a more complete list of ways to spell object names, see @@ -101,36 +101,36 @@
OPTIONS
- -t
Instead of the content, show the object type identified by -<object>.
+<object>.- -s
Instead of the content, show the object size identified by -<object>.
+<object>.- -e
- -
Exit with zero status if <object> exists and is a valid -object. If <object> is of an invalid format exit with non-zero and +
Exit with zero status if <object> exists and is a valid +object. If <object> is of an invalid format exit with non-zero and emits an error on stderr.
- -p
- -
Pretty-print the contents of <object> based on its type.
+Pretty-print the contents of <object> based on its type.
- <type>
- -
Typically this matches the real type of <object> but asking +
Typically this matches the real type of <object> but asking for a type that can trivially be dereferenced from the given -<object> is also permitted. An example is to ask for a -"tree" with <object> being a commit object that contains it, -or to ask for a "blob" with <object> being a tag object that +<object> is also permitted. An example is to ask for a +"tree" with <object> being a commit object that contains it, +or to ask for a "blob" with <object> being a tag object that points at it.
- --textconv
- @@ -138,8 +138,8 @@
Show the content as transformed by a textconv filter. In this case, -<object> has to be of the form <tree-ish>:<path>, or :<path> in +<object> has to be of the form <tree-ish>:<path>, or :<path> in order to apply the filter to the content recorded in the index at <path>.
OPTIONS
Show the content as converted by the filters configured in the current working tree for the given <path> (i.e. smudge filters, -end-of-line conversion, etc). In this case, <object> has to be of -the form <tree-ish>:<path>, or :<path>.
+end-of-line conversion, etc). In this case, <object> has to be of +the form <tree-ish>:<path>, or :<path>.- --path=<path>
- @@ -293,16 +293,16 @@
OUTPUT
If
-tis specified, one of the <type>.-If
+-sis specified, the size of the <object> in bytes.If
-sis specified, the size of the <object> in bytes.-If
+-eis specified, no output, unless the <object> is malformed.If
-eis specified, no output, unless the <object> is malformed.-If
+-pis specified, the contents of <object> are pretty-printed.If
-pis specified, the contents of <object> are pretty-printed.-If <type> is specified, the raw (though uncompressed) contents of the <object> +
If <type> is specified, the raw (though uncompressed) contents of the <object> will be returned.
BATCH OUTPUT<
-<object> SP missing LF+<object> SP missing LF-<object> SP ambiguous LF+<object> SP ambiguous LF-<object> SP missing LF+<object> SP missing LF@@ -433,7 +433,7 @@BATCH OUTPUT<
dangling SP <size> LF -<object> LF+<object> LF@@ -443,7 +443,7 @@BATCH OUTPUT<
loop SP <size> LF -<object> LF+<object> LF@@ -453,7 +453,7 @@BATCH OUTPUT<
notdir SP <size> LF -<object> LF+<object> LFdiff --git a/external/docs/content/docs/git-cat-file/2.32.0.html b/external/docs/content/docs/git-cat-file/2.32.0.html index 2659c60e7c..13faba6929 100644 --- a/external/docs/content/docs/git-cat-file/2.32.0.html +++ b/external/docs/content/docs/git-cat-file/2.32.0.html @@ -55,7 +55,7 @@NAME
SYNOPSIS
@@ -84,7 +84,7 @@-git cat-file (-t [--allow-unknown-type]| -s [--allow-unknown-type]| -e | -p | <type> | --textconv | --filters ) [--path=<path>] <object> +git cat-file (-t [--allow-unknown-type]| -s [--allow-unknown-type]| -e | -p | <type> | --textconv | --filters ) [--path=<path>] <object> git cat-file (--batch[=<format>] | --batch-check[=<format>]) [ --textconv | --filters ] [--follow-symlinks]OPTIONS
@@ -384,7 +384,7 @@-
- <object>
+- <object>
The name of the object to show. For a more complete list of ways to spell object names, see @@ -93,36 +93,36 @@
OPTIONS
- -t
Instead of the content, show the object type identified by -<object>.
+<object>.- -s
Instead of the content, show the object size identified by -<object>.
+<object>.- -e
- -
Exit with zero status if <object> exists and is a valid -object. If <object> is of an invalid format exit with non-zero and +
Exit with zero status if <object> exists and is a valid +object. If <object> is of an invalid format exit with non-zero and emits an error on stderr.
- -p
- -
Pretty-print the contents of <object> based on its type.
+Pretty-print the contents of <object> based on its type.
- <type>
- -
Typically this matches the real type of <object> but asking +
Typically this matches the real type of <object> but asking for a type that can trivially be dereferenced from the given -<object> is also permitted. An example is to ask for a -"tree" with <object> being a commit object that contains it, -or to ask for a "blob" with <object> being a tag object that +<object> is also permitted. An example is to ask for a +"tree" with <object> being a commit object that contains it, +or to ask for a "blob" with <object> being a tag object that points at it.
- --textconv
- @@ -130,8 +130,8 @@
Show the content as transformed by a textconv filter. In this case, -<object> has to be of the form <tree-ish>
:<path>, or:<path> in +<object> has to be of the form <tree-ish>:<path>, or:<path> in order to apply the filter to the content recorded in the index at <path>.OPTIONS
Show the content as converted by the filters configured in the current working tree for the given <path> (i.e. smudge filters, -end-of-line conversion, etc). In this case, <object> has to be of -the form <tree-ish>
+end-of-line conversion, etc). In this case, <object> has to be of +the form <tree-ish>:<path>, or:<path>.:<path>, or:<path>.- --path=<path>
- @@ -285,16 +285,16 @@
OUTPUT
If
-tis specified, one of the <type>.-If
+-sis specified, the size of the <object> in bytes.If
-sis specified, the size of the <object> in bytes.-If
+-eis specified, no output, unless the <object> is malformed.If
-eis specified, no output, unless the <object> is malformed.-If
+-pis specified, the contents of <object> are pretty-printed.If
-pis specified, the contents of <object> are pretty-printed.-If <type> is specified, the raw (though uncompressed) contents of the <object> +
If <type> is specified, the raw (though uncompressed) contents of the <object> will be returned.
BATCH OUTPUT<
-<object> SP missing LF+<object> SP missing LF-<object> SP ambiguous LF+<object> SP ambiguous LF-<object> SP missing LF+<object> SP missing LF@@ -426,7 +426,7 @@BATCH OUTPUT<
dangling SP <size> LF -<object> LF+<object> LF@@ -436,7 +436,7 @@BATCH OUTPUT<
loop SP <size> LF -<object> LF+<object> LF@@ -446,7 +446,7 @@BATCH OUTPUT<
notdir SP <size> LF -<object> LF+<object> LFdiff --git a/external/docs/content/docs/git-cat-file/2.34.0.html b/external/docs/content/docs/git-cat-file/2.34.0.html index 279d810dda..b92d3e36c3 100644 --- a/external/docs/content/docs/git-cat-file/2.34.0.html +++ b/external/docs/content/docs/git-cat-file/2.34.0.html @@ -56,7 +56,7 @@NAME
SYNOPSIS
@@ -85,7 +85,7 @@-git cat-file (-t [--allow-unknown-type]| -s [--allow-unknown-type]| -e | -p | <type> | --textconv | --filters ) [--path=<path>] <object> +git cat-file (-t [--allow-unknown-type]| -s [--allow-unknown-type]| -e | -p | <type> | --textconv | --filters ) [--path=<path>] <object> git cat-file (--batch[=<format>] | --batch-check[=<format>]) [ --textconv | --filters ] [--follow-symlinks]OPTIONS
@@ -387,7 +387,7 @@-
- <object>
+- <object>
The name of the object to show. For a more complete list of ways to spell object names, see @@ -94,36 +94,36 @@
OPTIONS
- -t
Instead of the content, show the object type identified by -<object>.
+<object>.- -s
Instead of the content, show the object size identified by -<object>.
+<object>.- -e
- -
Exit with zero status if <object> exists and is a valid -object. If <object> is of an invalid format exit with non-zero and +
Exit with zero status if <object> exists and is a valid +object. If <object> is of an invalid format exit with non-zero and emits an error on stderr.
- -p
- -
Pretty-print the contents of <object> based on its type.
+Pretty-print the contents of <object> based on its type.
- <type>
- -
Typically this matches the real type of <object> but asking +
Typically this matches the real type of <object> but asking for a type that can trivially be dereferenced from the given -<object> is also permitted. An example is to ask for a -"tree" with <object> being a commit object that contains it, -or to ask for a "blob" with <object> being a tag object that +<object> is also permitted. An example is to ask for a +"tree" with <object> being a commit object that contains it, +or to ask for a "blob" with <object> being a tag object that points at it.
- --textconv
- @@ -131,8 +131,8 @@
Show the content as transformed by a textconv filter. In this case, -<object> has to be of the form <tree-ish>
:<path>, or:<path> in +<object> has to be of the form <tree-ish>:<path>, or:<path> in order to apply the filter to the content recorded in the index at <path>.OPTIONS
Show the content as converted by the filters configured in the current working tree for the given <path> (i.e. smudge filters, -end-of-line conversion, etc). In this case, <object> has to be of -the form <tree-ish>
+end-of-line conversion, etc). In this case, <object> has to be of +the form <tree-ish>:<path>, or:<path>.:<path>, or:<path>.- --path=<path>
- @@ -288,16 +288,16 @@
OUTPUT
If
-tis specified, one of the <type>.-If
+-sis specified, the size of the <object> in bytes.If
-sis specified, the size of the <object> in bytes.-If
+-eis specified, no output, unless the <object> is malformed.If
-eis specified, no output, unless the <object> is malformed.-If
+-pis specified, the contents of <object> are pretty-printed.If
-pis specified, the contents of <object> are pretty-printed.-If <type> is specified, the raw (though uncompressed) contents of the <object> +
If <type> is specified, the raw (though uncompressed) contents of the <object> will be returned.
BATCH OUTPUT<
-<object> SP missing LF+<object> SP missing LF-<object> SP ambiguous LF+<object> SP ambiguous LF-<object> SP missing LF+<object> SP missing LF@@ -429,7 +429,7 @@BATCH OUTPUT<
dangling SP <size> LF -<object> LF+<object> LF@@ -439,7 +439,7 @@BATCH OUTPUT<
loop SP <size> LF -<object> LF+<object> LF@@ -449,7 +449,7 @@BATCH OUTPUT<
notdir SP <size> LF -<object> LF+<object> LFdiff --git a/external/docs/content/docs/git-cat-file/2.36.0.html b/external/docs/content/docs/git-cat-file/2.36.0.html index de120348a3..a18086d910 100644 --- a/external/docs/content/docs/git-cat-file/2.36.0.html +++ b/external/docs/content/docs/git-cat-file/2.36.0.html @@ -53,9 +53,9 @@NAME
SYNOPSIS
-git cat-file <type> <object> -git cat-file (-e | -p) <object> -git cat-file (-t | -s) [--allow-unknown-type] <object> +git cat-file <type> <object> +git cat-file (-e | -p) <object> +git cat-file (-t | -s) [--allow-unknown-type] <object> git cat-file (--batch | --batch-check | --batch-command) [--batch-all-objects] [--buffer] [--follow-symlinks] [--unordered] [--textconv | --filters] @@ -88,7 +88,7 @@OPTIONS
-
- <object>
+- <object>
The name of the object to show. For a more complete list of ways to spell object names, see @@ -97,36 +97,36 @@
OPTIONS
- -t
Instead of the content, show the object type identified by -<object>.
+<object>.- -s
Instead of the content, show the object size identified by -<object>.
+<object>.- -e
- -
Exit with zero status if <object> exists and is a valid -object. If <object> is of an invalid format exit with non-zero and +
Exit with zero status if <object> exists and is a valid +object. If <object> is of an invalid format exit with non-zero and emits an error on stderr.
- -p
- -
Pretty-print the contents of <object> based on its type.
+Pretty-print the contents of <object> based on its type.
- <type>
- -
Typically this matches the real type of <object> but asking +
Typically this matches the real type of <object> but asking for a type that can trivially be dereferenced from the given -<object> is also permitted. An example is to ask for a -"tree" with <object> being a commit object that contains it, -or to ask for a "blob" with <object> being a tag object that +<object> is also permitted. An example is to ask for a +"tree" with <object> being a commit object that contains it, +or to ask for a "blob" with <object> being a tag object that points at it.
- --textconv
- @@ -134,8 +134,8 @@
Show the content as transformed by a textconv filter. In this case, -<object> has to be of the form <tree-ish>
:<path>, or:<path> in +<object> has to be of the form <tree-ish>:<path>, or:<path> in order to apply the filter to the content recorded in the index at <path>.OPTIONS
Show the content as converted by the filters configured in the current working tree for the given <path> (i.e. smudge filters, -end-of-line conversion, etc). In this case, <object> has to be of -the form <tree-ish>
+end-of-line conversion, etc). In this case, <object> has to be of +the form <tree-ish>:<path>, or:<path>.:<path>, or:<path>.- --path=<path>
- @@ -176,14 +176,14 @@
OPTIONS
@@ -435,7 +435,7 @@-
- contents <object>
+- contents <object>
- -
-Print object contents for object reference <object>. This corresponds to +
Print object contents for object reference <object>. This corresponds to the output of
--batch.- info <object>
+- info <object>
- -
Print object info for object reference <object>. This corresponds to the +
Print object info for object reference <object>. This corresponds to the output of
--batch-check.- flush
@@ -328,16 +328,16 @@OUTPUT
If
-tis specified, one of the <type>.-If
+-sis specified, the size of the <object> in bytes.If
-sis specified, the size of the <object> in bytes.-If
+-eis specified, no output, unless the <object> is malformed.If
-eis specified, no output, unless the <object> is malformed.-If
+-pis specified, the contents of <object> are pretty-printed.If
-pis specified, the contents of <object> are pretty-printed.-If <type> is specified, the raw (though uncompressed) contents of the <object> +
If <type> is specified, the raw (though uncompressed) contents of the <object> will be returned.
BATCH OUTPUT<
-<object> SP missing LF+<object> SP missing LF-<object> SP ambiguous LF+<object> SP ambiguous LF-<object> SP missing LF+<object> SP missing LF@@ -477,7 +477,7 @@BATCH OUTPUT<
dangling SP <size> LF -<object> LF+<object> LF@@ -487,7 +487,7 @@BATCH OUTPUT<
loop SP <size> LF -<object> LF+<object> LF@@ -497,7 +497,7 @@BATCH OUTPUT<
notdir SP <size> LF -<object> LF+<object> LFdiff --git a/external/docs/content/docs/git-cat-file/2.38.0.html b/external/docs/content/docs/git-cat-file/2.38.0.html index a31998efc4..2370221db5 100644 --- a/external/docs/content/docs/git-cat-file/2.38.0.html +++ b/external/docs/content/docs/git-cat-file/2.38.0.html @@ -50,9 +50,9 @@NAME
SYNOPSIS
-git cat-file <type> <object> -git cat-file (-e | -p) <object> -git cat-file (-t | -s) [--allow-unknown-type] <object> +git cat-file <type> <object> +git cat-file (-e | -p) <object> +git cat-file (-t | -s) [--allow-unknown-type] <object> git cat-file (--batch | --batch-check | --batch-command) [--batch-all-objects] [--buffer] [--follow-symlinks] [--unordered] [--textconv | --filters] [-z] @@ -85,7 +85,7 @@OPTIONS
-
- <object>
+- <object>
The name of the object to show. For a more complete list of ways to spell object names, see @@ -94,30 +94,30 @@
OPTIONS
- -t
Instead of the content, show the object type identified by -<object>.
+<object>.- -s
Instead of the content, show the object size identified by -<object>.
+<object>.- -e
- -
Exit with zero status if <object> exists and is a valid -object. If <object> is of an invalid format exit with non-zero and +
Exit with zero status if <object> exists and is a valid +object. If <object> is of an invalid format exit with non-zero and emits an error on stderr.
- -p
- -
Pretty-print the contents of <object> based on its type.
+Pretty-print the contents of <object> based on its type.
- <type>
- -
Typically this matches the real type of <object> but asking +
Typically this matches the real type of <object> but asking for a type that can trivially be dereferenced from the given -<object> is also permitted. An example is to ask for a -"tree" with <object> being a commit object that contains it, -or to ask for a "blob" with <object> being a tag object that +<object> is also permitted. An example is to ask for a +"tree" with <object> being a commit object that contains it, +or to ask for a "blob" with <object> being a tag object that points at it.
- --[no-]mailmap
@@ -130,7 +130,7 @@OPTIONS
- --textconv
- @@ -138,8 +138,8 @@
Show the content as transformed by a textconv filter. In this case, -<object> has to be of the form <tree-ish>
:<path>, or:<path> in +<object> has to be of the form <tree-ish>:<path>, or:<path> in order to apply the filter to the content recorded in the index at <path>.OPTIONS
Show the content as converted by the filters configured in the current working tree for the given <path> (i.e. smudge filters, -end-of-line conversion, etc). In this case, <object> has to be of -the form <tree-ish>
+end-of-line conversion, etc). In this case, <object> has to be of +the form <tree-ish>:<path>, or:<path>.:<path>, or:<path>.- --path=<path>
- @@ -180,14 +180,14 @@
OPTIONS
@@ -445,7 +445,7 @@-
- contents <object>
+- contents <object>
- -
-Print object contents for object reference <object>. This corresponds to +
Print object contents for object reference <object>. This corresponds to the output of
--batch.- info <object>
+- info <object>
- -
Print object info for object reference <object>. This corresponds to the +
Print object info for object reference <object>. This corresponds to the output of
--batch-check.- flush
@@ -338,16 +338,16 @@OUTPUT
If
-tis specified, one of the <type>.-If
+-sis specified, the size of the <object> in bytes.If
-sis specified, the size of the <object> in bytes.-If
+-eis specified, no output, unless the <object> is malformed.If
-eis specified, no output, unless the <object> is malformed.-If
+-pis specified, the contents of <object> are pretty-printed.If
-pis specified, the contents of <object> are pretty-printed.-If <type> is specified, the raw (though uncompressed) contents of the <object> +
If <type> is specified, the raw (though uncompressed) contents of the <object> will be returned.
BATCH OUTPUT<
-<object> SP missing LF+<object> SP missing LF-<object> SP ambiguous LF+<object> SP ambiguous LF-<object> SP missing LF+<object> SP missing LF@@ -487,7 +487,7 @@BATCH OUTPUT<
dangling SP <size> LF -<object> LF+<object> LF@@ -497,7 +497,7 @@BATCH OUTPUT<
loop SP <size> LF -<object> LF+<object> LF@@ -507,7 +507,7 @@BATCH OUTPUT<
notdir SP <size> LF -<object> LF+<object> LFdiff --git a/external/docs/content/docs/git-cat-file/2.40.0.html b/external/docs/content/docs/git-cat-file/2.40.0.html index 6baeb7a29d..12cac8dcad 100644 --- a/external/docs/content/docs/git-cat-file/2.40.0.html +++ b/external/docs/content/docs/git-cat-file/2.40.0.html @@ -47,9 +47,9 @@NAME
SYNOPSIS
-git cat-file <type> <object> -git cat-file (-e | -p) <object> -git cat-file (-t | -s) [--allow-unknown-type] <object> +git cat-file <type> <object> +git cat-file (-e | -p) <object> +git cat-file (-t | -s) [--allow-unknown-type] <object> git cat-file (--batch | --batch-check | --batch-command) [--batch-all-objects] [--buffer] [--follow-symlinks] [--unordered] [--textconv | --filters] [-z] @@ -82,7 +82,7 @@OPTIONS
-
- <object>
+- <object>
The name of the object to show. For a more complete list of ways to spell object names, see @@ -91,32 +91,32 @@
OPTIONS
- -t
Instead of the content, show the object type identified by -<object>.
+<object>.- -s
Instead of the content, show the object size identified by -<object>. If used with
--use-mailmapoption, will show +<object>. If used with--use-mailmapoption, will show the size of updated object after replacing idents using the mailmap mechanism.- -e
- -
Exit with zero status if <object> exists and is a valid -object. If <object> is of an invalid format exit with non-zero and +
Exit with zero status if <object> exists and is a valid +object. If <object> is of an invalid format exit with non-zero and emits an error on stderr.
- -p
- -
Pretty-print the contents of <object> based on its type.
+Pretty-print the contents of <object> based on its type.
- <type>
- -
Typically this matches the real type of <object> but asking +
Typically this matches the real type of <object> but asking for a type that can trivially be dereferenced from the given -<object> is also permitted. An example is to ask for a -"tree" with <object> being a commit object that contains it, -or to ask for a "blob" with <object> being a tag object that +<object> is also permitted. An example is to ask for a +"tree" with <object> being a commit object that contains it, +or to ask for a "blob" with <object> being a tag object that points at it.
- --[no-]mailmap
@@ -129,7 +129,7 @@OPTIONS
- --textconv
- @@ -137,8 +137,8 @@
Show the content as transformed by a textconv filter. In this case, -<object> has to be of the form <tree-ish>
:<path>, or:<path> in +<object> has to be of the form <tree-ish>:<path>, or:<path> in order to apply the filter to the content recorded in the index at <path>.OPTIONS
Show the content as converted by the filters configured in the current working tree for the given <path> (i.e. smudge filters, -end-of-line conversion, etc). In this case, <object> has to be of -the form <tree-ish>
+end-of-line conversion, etc). In this case, <object> has to be of +the form <tree-ish>:<path>, or:<path>.:<path>, or:<path>.- --path=<path>
- @@ -231,14 +231,14 @@
OPTIONS
@@ -496,7 +496,7 @@-
- contents <object>
+- contents <object>
- -
-Print object contents for object reference <object>. This corresponds to +
Print object contents for object reference <object>. This corresponds to the output of
--batch.- info <object>
+- info <object>
- -
Print object info for object reference <object>. This corresponds to the +
Print object info for object reference <object>. This corresponds to the output of
--batch-check.- flush
@@ -389,16 +389,16 @@OUTPUT
If
-tis specified, one of the <type>.-If
+-sis specified, the size of the <object> in bytes.If
-sis specified, the size of the <object> in bytes.-If
+-eis specified, no output, unless the <object> is malformed.If
-eis specified, no output, unless the <object> is malformed.-If
+-pis specified, the contents of <object> are pretty-printed.If
-pis specified, the contents of <object> are pretty-printed.-If <type> is specified, the raw (though uncompressed) contents of the <object> +
If <type> is specified, the raw (though uncompressed) contents of the <object> will be returned.
BATCH OUTPUT<
-<object> SP missing LF+<object> SP missing LF-<object> SP ambiguous LF+<object> SP ambiguous LF-<object> SP missing LF+<object> SP missing LF@@ -538,7 +538,7 @@BATCH OUTPUT<
dangling SP <size> LF -<object> LF+<object> LF@@ -548,7 +548,7 @@BATCH OUTPUT<
loop SP <size> LF -<object> LF+<object> LF@@ -558,7 +558,7 @@BATCH OUTPUT<
notdir SP <size> LF -<object> LF+<object> LFdiff --git a/external/docs/content/docs/git-cat-file/2.42.0.html b/external/docs/content/docs/git-cat-file/2.42.0.html index 8735f351bb..e8f701f7a7 100644 --- a/external/docs/content/docs/git-cat-file/2.42.0.html +++ b/external/docs/content/docs/git-cat-file/2.42.0.html @@ -39,9 +39,9 @@NAME
SYNOPSIS
-git cat-file <type> <object> -git cat-file (-e | -p) <object> -git cat-file (-t | -s) [--allow-unknown-type] <object> +git cat-file <type> <object> +git cat-file (-e | -p) <object> +git cat-file (-t | -s) [--allow-unknown-type] <object> git cat-file (--batch | --batch-check | --batch-command) [--batch-all-objects] [--buffer] [--follow-symlinks] [--unordered] [--textconv | --filters] [-Z] @@ -74,7 +74,7 @@OPTIONS
-
- <object>
+- <object>
The name of the object to show. For a more complete list of ways to spell object names, see @@ -83,32 +83,32 @@
OPTIONS
- -t
Instead of the content, show the object type identified by -<object>.
+<object>.- -s
Instead of the content, show the object size identified by -<object>. If used with
--use-mailmapoption, will show +<object>. If used with--use-mailmapoption, will show the size of updated object after replacing idents using the mailmap mechanism.- -e
- -
Exit with zero status if <object> exists and is a valid -object. If <object> is of an invalid format exit with non-zero and +
Exit with zero status if <object> exists and is a valid +object. If <object> is of an invalid format exit with non-zero and emits an error on stderr.
- -p
- -
Pretty-print the contents of <object> based on its type.
+Pretty-print the contents of <object> based on its type.
- <type>
- -
Typically this matches the real type of <object> but asking +
Typically this matches the real type of <object> but asking for a type that can trivially be dereferenced from the given -<object> is also permitted. An example is to ask for a -"tree" with <object> being a commit object that contains it, -or to ask for a "blob" with <object> being a tag object that +<object> is also permitted. An example is to ask for a +"tree" with <object> being a commit object that contains it, +or to ask for a "blob" with <object> being a tag object that points at it.
- --[no-]mailmap
@@ -121,7 +121,7 @@OPTIONS
- --textconv
- @@ -129,8 +129,8 @@
Show the content as transformed by a textconv filter. In this case, -<object> has to be of the form <tree-ish>
:<path>, or:<path> in +<object> has to be of the form <tree-ish>:<path>, or:<path> in order to apply the filter to the content recorded in the index at <path>.OPTIONS
Show the content as converted by the filters configured in the current working tree for the given <path> (i.e. smudge filters, -end-of-line conversion, etc). In this case, <object> has to be of -the form <tree-ish>
+end-of-line conversion, etc). In this case, <object> has to be of +the form <tree-ish>:<path>, or:<path>.:<path>, or:<path>.- --path=<path>
- @@ -223,14 +223,14 @@
OPTIONS
@@ -495,7 +495,7 @@-
- contents <object>
+- contents <object>
- -
-Print object contents for object reference <object>. This corresponds to +
Print object contents for object reference <object>. This corresponds to the output of
--batch.- info <object>
+- info <object>
- -
Print object info for object reference <object>. This corresponds to the +
Print object info for object reference <object>. This corresponds to the output of
--batch-check.- flush
@@ -388,16 +388,16 @@OUTPUT
If
-tis specified, one of the <type>.-If
+-sis specified, the size of the <object> in bytes.If
-sis specified, the size of the <object> in bytes.-If
+-eis specified, no output, unless the <object> is malformed.If
-eis specified, no output, unless the <object> is malformed.-If
+-pis specified, the contents of <object> are pretty-printed.If
-pis specified, the contents of <object> are pretty-printed.-If <type> is specified, the raw (though uncompressed) contents of the <object> +
If <type> is specified, the raw (though uncompressed) contents of the <object> will be returned.
BATCH OUTPUT<
-<object> SP missing LF+<object> SP missing LF-<object> SP ambiguous LF+<object> SP ambiguous LF-<object> SP missing LF+<object> SP missing LF@@ -537,7 +537,7 @@BATCH OUTPUT<
dangling SP <size> LF -<object> LF+<object> LF@@ -547,7 +547,7 @@BATCH OUTPUT<
loop SP <size> LF -<object> LF+<object> LF@@ -557,7 +557,7 @@BATCH OUTPUT<
notdir SP <size> LF -<object> LF+<object> LFdiff --git a/external/docs/content/docs/git-cat-file/2.42.1.html b/external/docs/content/docs/git-cat-file/2.42.1.html index 83c0321be0..e2575785fe 100644 --- a/external/docs/content/docs/git-cat-file/2.42.1.html +++ b/external/docs/content/docs/git-cat-file/2.42.1.html @@ -61,9 +61,9 @@NAME
SYNOPSIS
-git cat-file <type> <object> -git cat-file (-e | -p) <object> -git cat-file (-t | -s) [--allow-unknown-type] <object> +git cat-file <type> <object> +git cat-file (-e | -p) <object> +git cat-file (-t | -s) [--allow-unknown-type] <object> git cat-file (--textconv | --filters) [<rev>:<path|tree-ish> | --path=<path|tree-ish> <rev>] git cat-file (--batch | --batch-check | --batch-command) [--batch-all-objects] @@ -97,7 +97,7 @@OPTIONS
-
- <object>
+- <object>
The name of the object to show. For a more complete list of ways to spell object names, see @@ -106,32 +106,32 @@
OPTIONS
- -t
Instead of the content, show the object type identified by -<object>.
+<object>.- -s
Instead of the content, show the object size identified by -<object>. If used with
--use-mailmapoption, will show +<object>. If used with--use-mailmapoption, will show the size of updated object after replacing idents using the mailmap mechanism.- -e
- -
Exit with zero status if <object> exists and is a valid -object. If <object> is of an invalid format, exit with non-zero +
Exit with zero status if <object> exists and is a valid +object. If <object> is of an invalid format, exit with non-zero status and emit an error on stderr.
- -p
- -
Pretty-print the contents of <object> based on its type.
+Pretty-print the contents of <object> based on its type.
- <type>
- -
Typically this matches the real type of <object> but asking +
Typically this matches the real type of <object> but asking for a type that can trivially be dereferenced from the given -<object> is also permitted. An example is to ask for a -"tree" with <object> being a commit object that contains it, -or to ask for a "blob" with <object> being a tag object that +<object> is also permitted. An example is to ask for a +"tree" with <object> being a commit object that contains it, +or to ask for a "blob" with <object> being a tag object that points at it.
- --[no-]mailmap
@@ -144,7 +144,7 @@OPTIONS
- --textconv
- @@ -152,8 +152,8 @@
Show the content as transformed by a textconv filter. In this case, -<object> has to be of the form <tree-ish>
:<path>, or:<path> in +<object> has to be of the form <tree-ish>:<path>, or:<path> in order to apply the filter to the content recorded in the index at <path>.OPTIONS
Show the content as converted by the filters configured in the current working tree for the given <path> (i.e. smudge filters, -end-of-line conversion, etc). In this case, <object> has to be of -the form <tree-ish>
+end-of-line conversion, etc). In this case, <object> has to be of +the form <tree-ish>:<path>, or:<path>.:<path>, or:<path>.- --path=<path>
- @@ -246,14 +246,14 @@
OPTIONS
@@ -518,7 +518,7 @@-
- contents <object>
+- contents <object>
- -
-Print object contents for object reference <object>. This corresponds to +
Print object contents for object reference <object>. This corresponds to the output of
--batch.- info <object>
+- info <object>
- -
Print object info for object reference <object>. This corresponds to the +
Print object info for object reference <object>. This corresponds to the output of
--batch-check.- flush
@@ -411,16 +411,16 @@OUTPUT
If
-tis specified, one of the <type>.-If
+-sis specified, the size of the <object> in bytes.If
-sis specified, the size of the <object> in bytes.-If
+-eis specified, no output, unless the <object> is malformed.If
-eis specified, no output, unless the <object> is malformed.-If
+-pis specified, the contents of <object> are pretty-printed.If
-pis specified, the contents of <object> are pretty-printed.-If <type> is specified, the raw (though uncompressed) contents of the <object> +
If <type> is specified, the raw (though uncompressed) contents of the <object> will be returned.
BATCH OUTPUT<
-<object> SP missing LF+<object> SP missing LF-<object> SP ambiguous LF+<object> SP ambiguous LF-<object> SP missing LF+<object> SP missing LF@@ -560,7 +560,7 @@BATCH OUTPUT<
dangling SP <size> LF -<object> LF+<object> LF@@ -570,7 +570,7 @@BATCH OUTPUT<
loop SP <size> LF -<object> LF+<object> LF@@ -580,7 +580,7 @@BATCH OUTPUT<
notdir SP <size> LF -<object> LF+<object> LFdiff --git a/external/docs/content/docs/git-cat-file/2.46.1.html b/external/docs/content/docs/git-cat-file/2.46.1.html index 83a6b98a66..9098ee5af2 100644 --- a/external/docs/content/docs/git-cat-file/2.46.1.html +++ b/external/docs/content/docs/git-cat-file/2.46.1.html @@ -51,9 +51,9 @@NAME
SYNOPSIS
-git cat-file <type> <object> -git cat-file (-e | -p) <object> -git cat-file (-t | -s) [--allow-unknown-type] <object> +git cat-file <type> <object> +git cat-file (-e | -p) <object> +git cat-file (-t | -s) [--allow-unknown-type] <object> git cat-file (--textconv | --filters) [<rev>:<path|tree-ish> | --path=<path|tree-ish> <rev>] git cat-file (--batch | --batch-check | --batch-command) [--batch-all-objects] @@ -87,7 +87,7 @@OPTIONS
-
- <object>
+- <object>
The name of the object to show. For a more complete list of ways to spell object names, see @@ -96,32 +96,32 @@
OPTIONS
- -t
Instead of the content, show the object type identified by -<object>.
+<object>.- -s
Instead of the content, show the object size identified by -<object>. If used with
--use-mailmapoption, will show +<object>. If used with--use-mailmapoption, will show the size of updated object after replacing idents using the mailmap mechanism.- -e
- -
Exit with zero status if <object> exists and is a valid -object. If <object> is of an invalid format, exit with non-zero +
Exit with zero status if <object> exists and is a valid +object. If <object> is of an invalid format, exit with non-zero status and emit an error on stderr.
- -p
- -
Pretty-print the contents of <object> based on its type.
+Pretty-print the contents of <object> based on its type.
- <type>
- -
Typically this matches the real type of <object> but asking +
Typically this matches the real type of <object> but asking for a type that can trivially be dereferenced from the given -<object> is also permitted. An example is to ask for a -"tree" with <object> being a commit object that contains it, -or to ask for a "blob" with <object> being a tag object that +<object> is also permitted. An example is to ask for a +"tree" with <object> being a commit object that contains it, +or to ask for a "blob" with <object> being a tag object that points at it.
- --[no-]mailmap
@@ -134,7 +134,7 @@OPTIONS
- --textconv
- @@ -142,8 +142,8 @@
Show the content as transformed by a textconv filter. In this case, -<object> has to be of the form <tree-ish>
:<path>, or:<path> in +<object> has to be of the form <tree-ish>:<path>, or:<path> in order to apply the filter to the content recorded in the index at <path>.OPTIONS
Show the content as converted by the filters configured in the current working tree for the given <path> (i.e. smudge filters, -end-of-line conversion, etc). In this case, <object> has to be of -the form <tree-ish>
+end-of-line conversion, etc). In this case, <object> has to be of +the form <tree-ish>:<path>, or:<path>.:<path>, or:<path>.- --path=<path>
- @@ -236,14 +236,14 @@
OPTIONS
@@ -508,7 +508,7 @@-
- contents <object>
+- contents <object>
- -
-Print object contents for object reference <object>. This corresponds to +
Print object contents for object reference <object>. This corresponds to the output of
--batch.- info <object>
+- info <object>
- -
Print object info for object reference <object>. This corresponds to the +
Print object info for object reference <object>. This corresponds to the output of
--batch-check.- flush
@@ -401,16 +401,16 @@OUTPUT
If
-tis specified, one of the <type>.-If
+-sis specified, the size of the <object> in bytes.If
-sis specified, the size of the <object> in bytes.-If
+-eis specified, no output, unless the <object> is malformed.If
-eis specified, no output, unless the <object> is malformed.-If
+-pis specified, the contents of <object> are pretty-printed.If
-pis specified, the contents of <object> are pretty-printed.-If <type> is specified, the raw (though uncompressed) contents of the <object> +
If <type> is specified, the raw (though uncompressed) contents of the <object> will be returned.
BATCH OUTPUT<
-<object> SP missing LF+<object> SP missing LF-<object> SP ambiguous LF+<object> SP ambiguous LF-<object> SP missing LF+<object> SP missing LF@@ -550,7 +550,7 @@BATCH OUTPUT<
dangling SP <size> LF -<object> LF+<object> LF@@ -560,7 +560,7 @@BATCH OUTPUT<
loop SP <size> LF -<object> LF+<object> LF@@ -570,7 +570,7 @@BATCH OUTPUT<
notdir SP <size> LF -<object> LF+<object> LFdiff --git a/external/docs/content/docs/git-cat-file/2.5.6.html b/external/docs/content/docs/git-cat-file/2.5.6.html index c5ae688868..3256a1a709 100644 --- a/external/docs/content/docs/git-cat-file/2.5.6.html +++ b/external/docs/content/docs/git-cat-file/2.5.6.html @@ -39,7 +39,7 @@NAME
SYNOPSIS
@@ -64,7 +64,7 @@-git cat-file (-t [--allow-unknown-type]| -s [--allow-unknown-type]| -e | -p | <type> | --textconv ) <object> +git cat-file (-t [--allow-unknown-type]| -s [--allow-unknown-type]| -e | -p | <type> | --textconv ) <object> git cat-file (--batch | --batch-check) [--follow-symlinks] < <list-of-objects>OPTIONS
@@ -317,7 +317,7 @@-
- <object>
+- <object>
The name of the object to show. For a more complete list of ways to spell object names, see @@ -73,35 +73,35 @@
OPTIONS
- -t
Instead of the content, show the object type identified by -<object>.
+<object>.- -s
Instead of the content, show the object size identified by -<object>.
+<object>.- -e
- -
Suppress all output; instead exit with zero status if <object> +
Suppress all output; instead exit with zero status if <object> exists and is a valid object.
- -p
- -
Pretty-print the contents of <object> based on its type.
+Pretty-print the contents of <object> based on its type.
- <type>
- -
Typically this matches the real type of <object> but asking +
Typically this matches the real type of <object> but asking for a type that can trivially be dereferenced from the given -<object> is also permitted. An example is to ask for a -"tree" with <object> being a commit object that contains it, -or to ask for a "blob" with <object> being a tag object that +<object> is also permitted. An example is to ask for a +"tree" with <object> being a commit object that contains it, +or to ask for a "blob" with <object> being a tag object that points at it.
- --textconv
Show the content as transformed by a textconv filter. In this case, -<object> has be of the form <tree-ish>:<path>, or :<path> in order +<object> has be of the form <tree-ish>:<path>, or :<path> in order to apply the filter to the content recorded in the index at <path>.
- --batch
@@ -219,16 +219,16 @@OUTPUT
If -t is specified, one of the <type>.
-If -s is specified, the size of the <object> in bytes.
+If -s is specified, the size of the <object> in bytes.
If -e is specified, no output.
-If -p is specified, the contents of <object> are pretty-printed.
+If -p is specified, the contents of <object> are pretty-printed.
-If <type> is specified, the raw (though uncompressed) contents of the <object> +
If <type> is specified, the raw (though uncompressed) contents of the <object> will be returned.
BATCH OUTPUT<
-<object> SP missing LF+<object> SP missing LF-<object> SP missing LF+<object> SP missing LF@@ -351,7 +351,7 @@BATCH OUTPUT<
dangling SP <size> LF -<object> LF+<object> LF@@ -361,7 +361,7 @@BATCH OUTPUT<
loop SP <size> LF -<object> LF+<object> LF@@ -371,7 +371,7 @@BATCH OUTPUT<
notdir SP <size> LF -<object> LF+<object> LFdiff --git a/external/docs/content/docs/git-cat-file/2.50.0.html b/external/docs/content/docs/git-cat-file/2.50.0.html index ffae5414ef..fe9f4102eb 100644 --- a/external/docs/content/docs/git-cat-file/2.50.0.html +++ b/external/docs/content/docs/git-cat-file/2.50.0.html @@ -40,8 +40,8 @@NAME
SYNOPSIS
-git cat-file <type> <object> -git cat-file (-e | -p | -t | -s) <object> +git cat-file <type> <object> +git cat-file (-e | -p | -t | -s) <object> git cat-file (--textconv | --filters) [<rev>:<path|tree-ish> | --path=<path|tree-ish> <rev>] git cat-file (--batch | --batch-check | --batch-command) [--batch-all-objects] @@ -75,7 +75,7 @@OPTIONS
-
- <object>
+- <object>
The name of the object to show. For a more complete list of ways to spell object names, see @@ -84,32 +84,32 @@
OPTIONS
- -t
Instead of the content, show the object type identified by -<object>.
+<object>.- -s
Instead of the content, show the object size identified by -<object>. If used with
--use-mailmapoption, will show +<object>. If used with--use-mailmapoption, will show the size of updated object after replacing idents using the mailmap mechanism.- -e
- -
Exit with zero status if <object> exists and is a valid -object. If <object> is of an invalid format, exit with non-zero +
Exit with zero status if <object> exists and is a valid +object. If <object> is of an invalid format, exit with non-zero status and emit an error on stderr.
- -p
- -
Pretty-print the contents of <object> based on its type.
+Pretty-print the contents of <object> based on its type.
- <type>
- -
Typically this matches the real type of <object> but asking +
Typically this matches the real type of <object> but asking for a type that can trivially be dereferenced from the given -<object> is also permitted. An example is to ask for a -"tree" with <object> being a commit object that contains it, -or to ask for a "blob" with <object> being a tag object that +<object> is also permitted. An example is to ask for a +"tree" with <object> being a commit object that contains it, +or to ask for a "blob" with <object> being a tag object that points at it.
- --[no-]mailmap
@@ -122,7 +122,7 @@OPTIONS
- --textconv
- @@ -130,8 +130,8 @@
Show the content as transformed by a textconv filter. In this case, -<object> has to be of the form <tree-ish>
:<path>, or:<path> in +<object> has to be of the form <tree-ish>:<path>, or:<path> in order to apply the filter to the content recorded in the index at <path>.OPTIONS
Show the content as converted by the filters configured in the current working tree for the given <path> (i.e. smudge filters, -end-of-line conversion, etc). In this case, <object> has to be of -the form <tree-ish>
+end-of-line conversion, etc). In this case, <object> has to be of +the form <tree-ish>:<path>, or:<path>.:<path>, or:<path>.- --filter=<filter-spec>
- --no-filter
@@ -247,14 +247,14 @@OPTIONS
@@ -515,7 +515,7 @@-
- contents <object>
+- contents <object>
- -
-Print object contents for object reference <object>. This corresponds to +
Print object contents for object reference <object>. This corresponds to the output of
--batch.- info <object>
+- info <object>
- -
Print object info for object reference <object>. This corresponds to the +
Print object info for object reference <object>. This corresponds to the output of
--batch-check.- flush
@@ -408,16 +408,16 @@OUTPUT
If
-tis specified, one of the <type>.-If
+-sis specified, the size of the <object> in bytes.If
-sis specified, the size of the <object> in bytes.-If
+-eis specified, no output, unless the <object> is malformed.If
-eis specified, no output, unless the <object> is malformed.-If
+-pis specified, the contents of <object> are pretty-printed.If
-pis specified, the contents of <object> are pretty-printed.-If <type> is specified, the raw (though uncompressed) contents of the <object> +
If <type> is specified, the raw (though uncompressed) contents of the <object> will be returned.
BATCH OUTPUT<
-<object> SP missing LF+<object> SP missing LF-<object> SP excluded LF+<object> SP excluded LF-<object> SP ambiguous LF+<object> SP ambiguous LF-<object> SP missing LF+<object> SP missing LF@@ -566,7 +566,7 @@BATCH OUTPUT<
dangling SP <size> LF -<object> LF+<object> LF@@ -576,7 +576,7 @@BATCH OUTPUT<
loop SP <size> LF -<object> LF+<object> LF@@ -586,7 +586,7 @@BATCH OUTPUT<
notdir SP <size> LF -<object> LF+<object> LFdiff --git a/external/docs/content/docs/git-cat-file/2.51.0.html b/external/docs/content/docs/git-cat-file/2.51.0.html index ff020438e3..0f58940e50 100644 --- a/external/docs/content/docs/git-cat-file/2.51.0.html +++ b/external/docs/content/docs/git-cat-file/2.51.0.html @@ -39,8 +39,8 @@NAME
SYNOPSIS
-git cat-file <type> <object> -git cat-file (-e | -p | -t | -s) <object> +git cat-file <type> <object> +git cat-file (-e | -p | -t | -s) <object> git cat-file (--textconv | --filters) [<rev>:<path|tree-ish> | --path=<path|tree-ish> <rev>] git cat-file (--batch | --batch-check | --batch-command) [--batch-all-objects] @@ -74,7 +74,7 @@OPTIONS
-
- <object>
+- <object>
The name of the object to show. For a more complete list of ways to spell object names, see @@ -83,32 +83,32 @@
OPTIONS
- -t
Instead of the content, show the object type identified by -<object>.
+<object>.- -s
Instead of the content, show the object size identified by -<object>. If used with
--use-mailmapoption, will show +<object>. If used with--use-mailmapoption, will show the size of updated object after replacing idents using the mailmap mechanism.- -e
- -
Exit with zero status if <object> exists and is a valid -object. If <object> is of an invalid format, exit with non-zero +
Exit with zero status if <object> exists and is a valid +object. If <object> is of an invalid format, exit with non-zero status and emit an error on stderr.
- -p
- -
Pretty-print the contents of <object> based on its type.
+Pretty-print the contents of <object> based on its type.
- <type>
- -
Typically this matches the real type of <object> but asking +
Typically this matches the real type of <object> but asking for a type that can trivially be dereferenced from the given -<object> is also permitted. An example is to ask for a -"tree" with <object> being a commit object that contains it, -or to ask for a "blob" with <object> being a tag object that +<object> is also permitted. An example is to ask for a +"tree" with <object> being a commit object that contains it, +or to ask for a "blob" with <object> being a tag object that points at it.
- --[no-]mailmap
@@ -121,7 +121,7 @@OPTIONS
- --textconv
- @@ -129,8 +129,8 @@
Show the content as transformed by a textconv filter. In this case, -<object> has to be of the form <tree-ish>
:<path>, or:<path> in +<object> has to be of the form <tree-ish>:<path>, or:<path> in order to apply the filter to the content recorded in the index at <path>.OPTIONS
Show the content as converted by the filters configured in the current working tree for the given <path> (i.e. smudge filters, -end-of-line conversion, etc). In this case, <object> has to be of -the form <tree-ish>
+end-of-line conversion, etc). In this case, <object> has to be of +the form <tree-ish>:<path>, or:<path>.:<path>, or:<path>.- --filter=<filter-spec>
- --no-filter
@@ -246,14 +246,14 @@OPTIONS
@@ -520,7 +520,7 @@-
- contents <object>
+- contents <object>
- -
-Print object contents for object reference <object>. This corresponds to +
Print object contents for object reference <object>. This corresponds to the output of
--batch.- info <object>
+- info <object>
- -
Print object info for object reference <object>. This corresponds to the +
Print object info for object reference <object>. This corresponds to the output of
--batch-check.- flush
@@ -407,16 +407,16 @@OUTPUT
If
-tis specified, one of the <type>.-If
+-sis specified, the size of the <object> in bytes.If
-sis specified, the size of the <object> in bytes.-If
+-eis specified, no output, unless the <object> is malformed.If
-eis specified, no output, unless the <object> is malformed.-If
+-pis specified, the contents of <object> are pretty-printed.If
-pis specified, the contents of <object> are pretty-printed.-If <type> is specified, the raw (though uncompressed) contents of the <object> +
If <type> is specified, the raw (though uncompressed) contents of the <object> will be returned.
BATCH OUTPUT<
-<object> SP missing LF+<object> SP missing LF-<object> SP excluded LF+<object> SP excluded LF-<object> SP ambiguous LF+<object> SP ambiguous LF-<object> SP missing LF+<object> SP missing LF@@ -581,7 +581,7 @@BATCH OUTPUT<
dangling SP <size> LF -<object> LF+<object> LF@@ -591,7 +591,7 @@BATCH OUTPUT<
loop SP <size> LF -<object> LF+<object> LF@@ -601,7 +601,7 @@BATCH OUTPUT<
notdir SP <size> LF -<object> LF+<object> LFdiff --git a/external/docs/content/docs/git-cat-file/2.6.7.html b/external/docs/content/docs/git-cat-file/2.6.7.html index 00d89ac794..351f0ffd12 100644 --- a/external/docs/content/docs/git-cat-file/2.6.7.html +++ b/external/docs/content/docs/git-cat-file/2.6.7.html @@ -41,7 +41,7 @@NAME
SYNOPSIS
@@ -66,7 +66,7 @@-git cat-file (-t [--allow-unknown-type]| -s [--allow-unknown-type]| -e | -p | <type> | --textconv ) <object> +git cat-file (-t [--allow-unknown-type]| -s [--allow-unknown-type]| -e | -p | <type> | --textconv ) <object> git cat-file (--batch | --batch-check) [--follow-symlinks]OPTIONS
@@ -335,7 +335,7 @@-
- <object>
+- <object>
The name of the object to show. For a more complete list of ways to spell object names, see @@ -75,35 +75,35 @@
OPTIONS
- -t
Instead of the content, show the object type identified by -<object>.
+<object>.- -s
Instead of the content, show the object size identified by -<object>.
+<object>.- -e
- -
Suppress all output; instead exit with zero status if <object> +
Suppress all output; instead exit with zero status if <object> exists and is a valid object.
- -p
- -
Pretty-print the contents of <object> based on its type.
+Pretty-print the contents of <object> based on its type.
- <type>
- -
Typically this matches the real type of <object> but asking +
Typically this matches the real type of <object> but asking for a type that can trivially be dereferenced from the given -<object> is also permitted. An example is to ask for a -"tree" with <object> being a commit object that contains it, -or to ask for a "blob" with <object> being a tag object that +<object> is also permitted. An example is to ask for a +"tree" with <object> being a commit object that contains it, +or to ask for a "blob" with <object> being a tag object that points at it.
- --textconv
Show the content as transformed by a textconv filter. In this case, -<object> has be of the form <tree-ish>:<path>, or :<path> in order +<object> has be of the form <tree-ish>:<path>, or :<path> in order to apply the filter to the content recorded in the index at <path>.
- --batch
@@ -237,16 +237,16 @@OUTPUT
If -t is specified, one of the <type>.
-If -s is specified, the size of the <object> in bytes.
+If -s is specified, the size of the <object> in bytes.
If -e is specified, no output.
-If -p is specified, the contents of <object> are pretty-printed.
+If -p is specified, the contents of <object> are pretty-printed.
-If <type> is specified, the raw (though uncompressed) contents of the <object> +
If <type> is specified, the raw (though uncompressed) contents of the <object> will be returned.
BATCH OUTPUT<
-<object> SP missing LF+<object> SP missing LF-<object> SP missing LF+<object> SP missing LF@@ -369,7 +369,7 @@BATCH OUTPUT<
dangling SP <size> LF -<object> LF+<object> LF@@ -379,7 +379,7 @@BATCH OUTPUT<
loop SP <size> LF -<object> LF+<object> LF@@ -389,7 +389,7 @@BATCH OUTPUT<
notdir SP <size> LF -<object> LF+<object> LFdiff --git a/external/docs/content/docs/git-cat-file/2.9.5.html b/external/docs/content/docs/git-cat-file/2.9.5.html index 8462b23441..52167c6bf6 100644 --- a/external/docs/content/docs/git-cat-file/2.9.5.html +++ b/external/docs/content/docs/git-cat-file/2.9.5.html @@ -40,7 +40,7 @@NAME
SYNOPSIS
@@ -65,7 +65,7 @@-git cat-file (-t [--allow-unknown-type]| -s [--allow-unknown-type]| -e | -p | <type> | --textconv ) <object> +git cat-file (-t [--allow-unknown-type]| -s [--allow-unknown-type]| -e | -p | <type> | --textconv ) <object> git cat-file (--batch | --batch-check) [--follow-symlinks]OPTIONS
@@ -334,7 +334,7 @@-
- <object>
+- <object>
The name of the object to show. For a more complete list of ways to spell object names, see @@ -74,35 +74,35 @@
OPTIONS
- -t
Instead of the content, show the object type identified by -<object>.
+<object>.- -s
Instead of the content, show the object size identified by -<object>.
+<object>.- -e
- -
Suppress all output; instead exit with zero status if <object> +
Suppress all output; instead exit with zero status if <object> exists and is a valid object.
- -p
- -
Pretty-print the contents of <object> based on its type.
+Pretty-print the contents of <object> based on its type.
- <type>
- -
Typically this matches the real type of <object> but asking +
Typically this matches the real type of <object> but asking for a type that can trivially be dereferenced from the given -<object> is also permitted. An example is to ask for a -"tree" with <object> being a commit object that contains it, -or to ask for a "blob" with <object> being a tag object that +<object> is also permitted. An example is to ask for a +"tree" with <object> being a commit object that contains it, +or to ask for a "blob" with <object> being a tag object that points at it.
- --textconv
Show the content as transformed by a textconv filter. In this case, -<object> has be of the form <tree-ish>:<path>, or :<path> in order +<object> has be of the form <tree-ish>:<path>, or :<path> in order to apply the filter to the content recorded in the index at <path>.
- --batch
@@ -236,16 +236,16 @@OUTPUT
If
-tis specified, one of the <type>.-If
+-sis specified, the size of the <object> in bytes.If
-sis specified, the size of the <object> in bytes.If
-eis specified, no output.-If
+-pis specified, the contents of <object> are pretty-printed.If
-pis specified, the contents of <object> are pretty-printed.-If <type> is specified, the raw (though uncompressed) contents of the <object> +
If <type> is specified, the raw (though uncompressed) contents of the <object> will be returned.
BATCH OUTPUT<
-<object> SP missing LF+<object> SP missing LF-<object> SP missing LF+<object> SP missing LF@@ -368,7 +368,7 @@BATCH OUTPUT<
dangling SP <size> LF -<object> LF+<object> LF@@ -378,7 +378,7 @@BATCH OUTPUT<
loop SP <size> LF -<object> LF+<object> LF@@ -388,7 +388,7 @@BATCH OUTPUT<
notdir SP <size> LF -<object> LF+<object> LFdiff --git a/external/docs/content/docs/git-cat-file/fr.html b/external/docs/content/docs/git-cat-file/fr.html index 26f4e6fe4e..95c995796a 100644 --- a/external/docs/content/docs/git-cat-file/fr.html +++ b/external/docs/content/docs/git-cat-file/fr.html @@ -73,13 +73,13 @@OPTIONS
@@ -394,7 +394,7 @@-
- <objet>
+- <objet>
Le nom de l’objet à afficher. Pour une liste plus complète des façons d’épeler les noms d’objets, voir la section « SPÉCIFICATION DE RÉVISIONS" dans gitrevisions[7].
- -t
- -
Au lieu du contenu, afficher le type d’objet identifié par <objet>.
+Au lieu du contenu, afficher le type d’objet identifié par <objet>.
- -s
- @@ -87,15 +87,15 @@
OPTIONS
- -e
- -
Sortir avec un statut nul si <objet> existe et est un objet valide. Si <objet> est d’un format invalide, sortir avec un état non-zéro et émettre une erreur sur stderr.
+Sortir avec un statut nul si <objet> existe et est un objet valide. Si <objet> est d’un format invalide, sortir avec un état non-zéro et émettre une erreur sur stderr.
- -p
- -
Formater l’affichage du contenu de <objet> en fonction de son type.
+Formater l’affichage du contenu de <objet> en fonction de son type.
- <type>
- -
Typiquement, cela correspond au type réel de <objet> mais la demande d’un type qui peut trivialement être déréférencé à partir du <objet> donné est également autorisée. Un exemple est de demander un "tree" avec <objet> étant un objet commit qui le contient, ou de demander un "blob" avec <objet> étant un objet tag qui le pointe.
+Typiquement, cela correspond au type réel de <objet> mais la demande d’un type qui peut trivialement être déréférencé à partir du <objet> donné est également autorisée. Un exemple est de demander un "tree" avec <objet> étant un objet commit qui le contient, ou de demander un "blob" avec <objet> étant un objet tag qui le pointe.
- --[no-]mailmap
- --[no-]use-mailmap
@@ -104,11 +104,11 @@OPTIONS
- --textconv
- -
Afficher le contenu tel que transformé par un filtre textconv. Dans ce cas, <objet> doit être de la forme <arbre-esque>
+:<chemin>, ou:<chemin> afin d’appliquer le filtre au contenu enregistré dans l’index à <chemin>.Afficher le contenu tel que transformé par un filtre textconv. Dans ce cas, <objet> doit être de la forme <arbre-esque>
:<chemin>, ou:<chemin> afin d’appliquer le filtre au contenu enregistré dans l’index à <chemin>.- --filters
- -
Afficher le contenu tel qu’il a été converti par les filtres configurés dans l’arbre de travail actuel pour le <chemin> donné (c’est-à-dire les filtres de maculage, la conversion de fin de ligne, etc). Dans ce cas, <objet> doit être de la forme <arbre-esque>
+:<chemin>, ou:<chemin>.Afficher le contenu tel qu’il a été converti par les filtres configurés dans l’arbre de travail actuel pour le <chemin> donné (c’est-à-dire les filtres de maculage, la conversion de fin de ligne, etc). Dans ce cas, <objet> doit être de la forme <arbre-esque>
:<chemin>, ou:<chemin>.- --filter=<spéc. du filtre>
- --no-filter
@@ -193,11 +193,11 @@OPTIONS
-
- contents <objet>
+- contents <objet>
- -
Print object contents for object reference <object>. This corresponds to the output of
--batch.- info <objet>
+- info <objet>
- @@ -313,16 +313,16 @@
Print object info for object reference <object>. This corresponds to the output of
--batch-check.SORTIE
Si
-test spécifié, un des <type>.-Si
+-sest spécifié, la taille de l'<objet> en octets.Si
-sest spécifié, la taille de l'<objet> en octets.-Si
+-eest spécifié, aucune sortie, à moins que le <objet> soit malformé.Si
-eest spécifié, aucune sortie, à moins que le <objet> soit malformé.-Si
+-pest spécifié, le contenu de <objet> est formatté à l’affichage.Si
-pest spécifié, le contenu de <objet> est formatté à l’affichage.-Si <type> est spécifié, le contenu brut (mais non compressé) de l'<objet> sera retourné.
+Si <type> est spécifié, le contenu brut (mais non compressé) de l'<objet> sera retourné.
SORTIE DE L
-<objet> SP missing LF+<objet> SP missing LF-<objet> SP excluded LF+<objet> SP excluded LF-<objet> SP ambiguous LF+<objet> SP ambiguous LF-<objet> SP missing LF+<objet> SP missing LF@@ -439,7 +439,7 @@SORTIE DE L
dangling SP <taille> LF -<objet> LF+<objet> LF@@ -448,7 +448,7 @@SORTIE DE L
loop SP <taille> LF -<objet> LF+<objet> LF@@ -457,7 +457,7 @@SORTIE DE L
notdir SP <taille> LF -<objet> LF+<objet> LFdiff --git a/external/docs/content/docs/git-cat-file/zh_HANS-CN.html b/external/docs/content/docs/git-cat-file/zh_HANS-CN.html index a073d808df..820e8a332e 100644 --- a/external/docs/content/docs/git-cat-file/zh_HANS-CN.html +++ b/external/docs/content/docs/git-cat-file/zh_HANS-CN.html @@ -71,29 +71,29 @@@@ -75,7 +75,7 @@选项
@@ -392,7 +392,7 @@-
- <对象>
+- <对象>
要显示的对象名称。 有关拼写对象名称的更完整列表，请参阅 gitrevisions[7] 中的 “指定修订” 部分。
- -t
- -
不显示内容，而是显示由 <对象> 标识的对象类型。
+不显示内容，而是显示由 <对象> 标识的对象类型。
- -s
- -
不显示内容，而是显示由 <对象> 标识的对象大小。如果与
+--use-mailmap选项一起使用，则会显示使用邮件映射机制替换标识符后更新对象的大小。不显示内容，而是显示由 <对象> 标识的对象大小。如果与
--use-mailmap选项一起使用，则会显示使用邮件映射机制替换标识符后更新对象的大小。- -e
- -
如果 <对象> 存在且是有效对象，则以零状态退出。如果 <对象> 的格式无效，则以非零状态退出，并在标准错误流上显示错误信息。
+如果 <对象> 存在且是有效对象，则以零状态退出。如果 <对象> 的格式无效，则以非零状态退出，并在标准错误流上显示错误信息。
- -p
- -
根据 <对象> 的类型漂亮地打印其内容。
+根据 <对象> 的类型漂亮地打印其内容。
- <类型>
- -
通常情况下，这与 <对象> 的真实类型相匹配，但也允许要求一个可以从给定的 <对象> 中简单地反向引用的类型。 例如，要求输入 “目录树”，而 <对象> 是包含它的提交对象，或者要求输入 "blob"，而 <对象> 是指向它的标记对象。
+通常情况下，这与 <对象> 的真实类型相匹配，但也允许要求一个可以从给定的 <对象> 中简单地反向引用的类型。 例如，要求输入 “目录树”，而 <对象> 是包含它的提交对象，或者要求输入 "blob"，而 <对象> 是指向它的标记对象。
- --[no-]mailmap
- --[no-]use-mailmap
@@ -102,11 +102,11 @@选项
- --textconv
- -
显示经 textconv 过滤器转换的内容。在这种情况下，<对象> 必须是 <目录树对象>
+:<路径> 或:<路径> 形式，以便将过滤器应用于 <路径> 处索引中记录的内容。显示经 textconv 过滤器转换的内容。在这种情况下，<对象> 必须是 <目录树对象>
:<路径> 或:<路径> 形式，以便将过滤器应用于 <路径> 处索引中记录的内容。- --filters
- -
显示经当前工作树中为给定的 <路径> 配置的过滤器（即污点过滤器、行结束符转换等）转换后的内容。在这种情况下，<对象> 的形式必须是`<目录树对象>:<路径>，或 `:<路径>。
+显示经当前工作树中为给定的 <路径> 配置的过滤器（即污点过滤器、行结束符转换等）转换后的内容。在这种情况下，<对象> 的形式必须是`<目录树对象>:<路径>，或 `:<路径>。
- --filter=<过滤器定义>
- --no-filter
@@ -191,13 +191,13 @@选项
-如果指定了
+-s，则是 <对象> 的大小（以字节为单位）。如果指定了
-s，则是 <对象> 的大小（以字节为单位）。-如果指定了
+-e，则没有输出，除非 <对象> 是畸形的。如果指定了
-e，则没有输出，除非 <对象> 是畸形的。-如果指定了
+-p，则会对 <对象> 的内容进行漂亮打印。如果指定了
-p，则会对 <对象> 的内容进行漂亮打印。-如果指定了 <类型>，则将返回 <对象> 的原始内容（尽管未压缩）。
+如果指定了 <类型>，则将返回 <对象> 的原始内容（尽管未压缩）。
批输出
-<对象> SP 丢失 LF+<对象> SP 丢失 LF-<对象> SP ambiguous LF+<对象> SP ambiguous LF-<对象> SP 丢失 LF+<对象> SP 丢失 LF@@ -437,7 +437,7 @@@@ -81,7 +81,7 @@批输出
dangling SP <尺寸> LF -<对象> LF+<对象> LF@@ -446,7 +446,7 @@@@ -110,7 +110,7 @@批输出
loop SP <尺寸> LF -<对象> LF+<对象> LF@@ -455,7 +455,7 @@@@ -92,7 +92,7 @@批输出
notdir SP <尺寸> LF -<对象> LF+<对象> LFdiff --git a/external/docs/content/docs/git-check-attr.html b/external/docs/content/docs/git-check-attr.html index 44273a4101..7d1b8743e8 100644 --- a/external/docs/content/docs/git-check-attr.html +++ b/external/docs/content/docs/git-check-attr.html @@ -40,8 +40,8 @@@@ -80,7 +80,7 @@NAME
SYNOPSIS
-git check-attr [--source <tree-ish>] [-a | --all | <attr>…] [--] <pathname>… -git check-attr --stdin [-z] [--source <tree-ish>] [-a | --all | <attr>…]+git check-attr [--source <tree-ish>] [-a | --all | <attr>…] [--] <pathname>… +git check-attr --stdin [-z] [--source <tree-ish>] [-a | --all | <attr>…]OPTIONS
If--stdinis also given, input paths are separated with a NUL character instead of a linefeed character. -- --source=<tree-ish>
+- --source=<tree-ish>
Check attributes against the specified tree-ish. It is common to specify the source tree by naming a commit, branch, or tag associated diff --git a/external/docs/content/docs/git-check-attr/2.40.0.html b/external/docs/content/docs/git-check-attr/2.40.0.html index 701980662d..24adc66dc2 100644 --- a/external/docs/content/docs/git-check-attr/2.40.0.html +++ b/external/docs/content/docs/git-check-attr/2.40.0.html @@ -52,8 +52,8 @@
NAME
SYNOPSIS
-git check-attr [--source <tree-ish>] [-a | --all | <attr>…] [--] <pathname>… -git check-attr --stdin [-z] [--source <tree-ish>] [-a | --all | <attr>…]+git check-attr [--source <tree-ish>] [-a | --all | <attr>…] [--] <pathname>… +git check-attr --stdin [-z] [--source <tree-ish>] [-a | --all | <attr>…]OPTIONS
If--stdinis also given, input paths are separated with a NUL character instead of a linefeed character. -- --source=<tree-ish>
+- --source=<tree-ish>
Check attributes against the specified tree-ish. It is common to specify the source tree by naming a commit, branch or tag associated diff --git a/external/docs/content/docs/git-check-attr/2.43.0.html b/external/docs/content/docs/git-check-attr/2.43.0.html index dbda27ba9b..9055ea76b2 100644 --- a/external/docs/content/docs/git-check-attr/2.43.0.html +++ b/external/docs/content/docs/git-check-attr/2.43.0.html @@ -70,8 +70,8 @@
NAME
SYNOPSIS
-git check-attr [--source <tree-ish>] [-a | --all | <attr>…] [--] <pathname>… -git check-attr --stdin [-z] [--source <tree-ish>] [-a | --all | <attr>…]+git check-attr [--source <tree-ish>] [-a | --all | <attr>…] [--] <pathname>… +git check-attr --stdin [-z] [--source <tree-ish>] [-a | --all | <attr>…]OPTIONS
If--stdinis also given, input paths are separated with a NUL character instead of a linefeed character. -- --source=<tree-ish>
+- --source=<tree-ish>
Check attributes against the specified tree-ish. It is common to specify the source tree by naming a commit, branch, or tag associated diff --git a/external/docs/content/docs/git-check-attr/2.50.0.html b/external/docs/content/docs/git-check-attr/2.50.0.html index cd2c6a4df5..0ee3a8249e 100644 --- a/external/docs/content/docs/git-check-attr/2.50.0.html +++ b/external/docs/content/docs/git-check-attr/2.50.0.html @@ -41,8 +41,8 @@
NAME
SYNOPSIS
-git check-attr [--source <tree-ish>] [-a | --all | <attr>…] [--] <pathname>… -git check-attr --stdin [-z] [--source <tree-ish>] [-a | --all | <attr>…]+git check-attr [--source <tree-ish>] [-a | --all | <attr>…] [--] <pathname>… +git check-attr --stdin [-z] [--source <tree-ish>] [-a | --all | <attr>…]OPTIONS
If--stdinis also given, input paths are separated with a NUL character instead of a linefeed character. -- --source=<tree-ish>
+- --source=<tree-ish>
Check attributes against the specified tree-ish. It is common to specify the source tree by naming a commit, branch, or tag associated diff --git a/external/docs/content/docs/git-check-attr/fr.html b/external/docs/content/docs/git-check-attr/fr.html index 4083836356..583c483e0a 100644 --- a/external/docs/content/docs/git-check-attr/fr.html +++ b/external/docs/content/docs/git-check-attr/fr.html @@ -41,8 +41,8 @@
NOM
SYNOPSIS
-git check-attr [--source <arbre-esque>] [-a | --all | <attr>…] [--] <nom-de-chemin>… -git check-attr --stdin [-z] [--source <arbre-esque>] [-a | --all | <attr>…]+git check-attr [--source <arbre-esque>] [-a | --all | <attr>…] [--] <nom-de-chemin>… +git check-attr --stdin [-z] [--source <arbre-esque>] [-a | --all | <attr>…]OPTIONS
- -
Le format de sortie est modifié pour être analysable par la machine. Si
--stdinest également donné, les chemins d’entrée sont séparés par un caractère NUL au lieu d’un caractère de saut de ligne.- --source=<arbre-esque>
+- --source=<arbre-esque>
- diff --git a/external/docs/content/docs/git-checkout-index/fr.html b/external/docs/content/docs/git-checkout-index/fr.html index bebf655399..18901a7733 100644 --- a/external/docs/content/docs/git-checkout-index/fr.html +++ b/external/docs/content/docs/git-checkout-index/fr.html @@ -39,7 +39,7 @@
Vérifier les attributs par rapport à l’arbre-esque spécifié. Il est courant de spécifier l’arbre source en nommant un commit, une branche ou une étiquette qui lui est associée.
NOM
SYNOPSIS
-@@ -67,25 +67,25 @@git checkout-index [-u] [-q] [-a] [-f] [-n] [--prefix=<chaîne>] +git checkout-index [-u] [-q] [-a] [-f] [-n] [--prefix=<chaîne>] [--stage=<nombre>|all] [--temp] [--ignore-skip-worktree-bits] @@ -86,7 +86,7 @@OPTIONS
- -
Ne pas extraire de nouveaux fichiers, seulement rafraîchir les fichiers déjà extraits.
- --prefix=<chaîne>
+- --prefix=<chaîne>
- diff --git a/external/docs/content/docs/git-checkout.html b/external/docs/content/docs/git-checkout.html index 21feb623c2..89751689a3 100644 --- a/external/docs/content/docs/git-checkout.html +++ b/external/docs/content/docs/git-checkout.html @@ -44,15 +44,15 @@
Lors de la création de fichiers, les préfixer avec <chaine> (généralement un répertoire incluant une terminaison /)
NAME
SYNOPSIS
-gitcheckout[-q] [-f] [-m] [<branch>] -gitcheckout[-q] [-f] [-m]--detach[<branch>] -gitcheckout[-q] [-f] [-m] [--detach] <commit> ++gitcheckout[-q] [-f] [-m] [<branch>] +gitcheckout[-q] [-f] [-m]--detach[<branch>] +gitcheckout[-q] [-f] [-m] [--detach] <commit>gitcheckout[-q] [-f] [-m] [[-b|-B|--orphan] <new-branch>] [<start-point>] -gitcheckout[-f] <tree-ish> [--] <pathspec>… -gitcheckout[-f] <tree-ish>--pathspec-from-file=<file> [--pathspec-file-nul] -gitcheckout[-f|--ours|--theirs|-m|--conflict=<style>] [--] <pathspec>… +gitcheckout[-f] <tree-ish> [--] <pathspec>… +gitcheckout[-f] <tree-ish>--pathspec-from-file=<file> [--pathspec-file-nul] +gitcheckout[-f|--ours|--theirs|-m|--conflict=<style>] [--] <pathspec>…gitcheckout[-f|--ours|--theirs|-m|--conflict=<style>]--pathspec-from-file=<file> [--pathspec-file-nul] -gitcheckout(-p|--patch) [<tree-ish>] [--] [<pathspec>…]gitcheckout(-p|--patch) [<tree-ish>] [--] [<pathspec>…]DESCRIPTION
@@ -60,25 +60,25 @@-
- +
gitcheckout[<branch>]gitcheckout[<branch>]- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing
+<branch>.HEADat the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name and
--no-guessis not specified, treat as equivalent to-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>-diff --git a/external/docs/content/docs/git-checkout/2.0.5.html b/external/docs/content/docs/git-checkout/2.0.5.html index 83ddf6a624..c4ab48b41f 100644 --- a/external/docs/content/docs/git-checkout/2.0.5.html +++ b/external/docs/content/docs/git-checkout/2.0.5.html @@ -40,12 +40,12 @@You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with rather expensive side-effects to show only the tracking information, if it exists, for the current branch.
@@ -105,8 +105,8 @@DESCRIPTION
--$ git branch -f <branch> [<start-point>] -$ git checkout <branch>+$ git branch -f <branch> [<start-point>] +$ git checkout <branch>- -
gitcheckout--detach[<branch>]- +
gitcheckout[--detach] <commit>- +
gitcheckout--detach[<branch>]gitcheckout[--detach] <commit>- -
-Prepare to work on top of <commit>, by detaching
HEADat it +Prepare to work on top of <commit>, by detaching
HEADat it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching--detachoption can be used to detachHEADat the tip of the branch (gitcheckout-<branch> would check out that branch without detachingHEAD).HEAD).-Omitting <branch> detaches
+HEADat the tip of the current branch.Omitting <branch> detaches
HEADat the tip of the current branch.- -
gitcheckout[-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>...- +
gitcheckout[-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>]--pathspec-from-file=<file> [--pathspec-file-nul]- +
gitcheckout[-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>...gitcheckout[-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>]--pathspec-from-file=<file> [--pathspec-file-nul]- -
Overwrite the contents of the files that match the pathspec. -When the <tree-ish> (most often a commit) is not given, +When the <tree-ish> (most often a commit) is not given, overwrite working tree with the contents in the index. -When the <tree-ish> is given, overwrite both the index and -the working tree with the contents at the <tree-ish>.
+When the <tree-ish> is given, overwrite both the index and +the working tree with the contents at the <tree-ish>.- +
gitcheckout(-p|--patch) [<tree-ish>] [--] [<pathspec>...]gitcheckout(-p|--patch) [<tree-ish>] [--] [<pathspec>...]This is similar to the previous mode, but lets you use the interactive interface to show the "diff" output and choose which @@ -256,21 +256,21 @@
OPTIONS
--guess--no-guess- -
If <branch> is not found but there does exist a tracking +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>@@ -292,8 +292,8 @@If the branch exists in multiple remotes and one of them is named by the
checkout.defaultRemoteconfiguration variable, we’ll use that -one for the purposes of disambiguation, even if the <branch> isn’t +one for the purposes of disambiguation, even if the <branch> isn’t unique across all remotes. Set it to e.g.checkout.defaultRemote=originto always checkout remote -branches from there if <branch> is ambiguous but exists on the +branches from there if <branch> is ambiguous but exists on the origin remote. See alsocheckout.defaultRemotein git-config[1].OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of
gitcheckout<commit> when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior ofgitcheckout<commit> when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.- @@ -369,9 +369,9 @@
--orphan<new-branch>OPTIONS
--patch- -
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the "Interactive Mode" @@ -426,8 +426,8 @@OPTIONS
In the default overlay mode,
+working tree, but not in <tree-ish> are removed, to make them +match <tree-ish> exactly.gitcheckoutnever removes files from the index or the working tree. When specifying--no-overlay, files that appear in the index and -working tree, but not in <tree-ish> are removed, to make them -match <tree-ish> exactly.--pathspec-from-file=<file>- @@ -444,7 +444,7 @@
-OPTIONS
separated with NUL character and all other characters are taken literally (including newlines and quotes).- <branch>
+- <branch>
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -476,7 +476,7 @@
OPTIONS
leave out at most one of <rev-a> and <rev-b>, in which case it defaults toHEAD.- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
@@ -490,7 +490,7 @@OPTIONS
- -
Do not interpret any more arguments as options.
- <pathspec>...
+- <pathspec>...
Limits the paths affected by the operation.
NAME
SYNOPSIS
-git checkout [-q] [-f] [-m] [<branch>] -git checkout [-q] [-f] [-m] --detach [<branch>] -git checkout [-q] [-f] [-m] [--detach] <commit> +git checkout [-q] [-f] [-m] [<branch>] +git checkout [-q] [-f] [-m] --detach [<branch>] +git checkout [-q] [-f] [-m] [--detach] <commit> git checkout [-q] [-f] [-m] [[-b|-B|--orphan] <new_branch>] [<start_point>] -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <paths>… -git checkout [-p|--patch] [<tree-ish>] [--] [<paths>…]+git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <paths>… +git checkout [-p|--patch] [<tree-ish>] [--] [<paths>…]DESCRIPTION
-
- git checkout <branch>
+- git checkout <branch>
- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing HEAD at the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.
+<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>-You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with a rather expensive side-effects to show only the tracking information, if exists, for the current branch.
@@ -98,8 +98,8 @@DESCRIPTION
--$ git branch -f <branch> [<start point>] -$ git checkout <branch>+$ git branch -f <branch> [<start point>] +$ git checkout <branch>- git checkout --detach [<branch>]
-- git checkout [--detach] <commit>
+- git checkout --detach [<branch>]
+- git checkout [--detach] <commit>
- -
-Prepare to work on top of <commit>, by detaching HEAD at it +
Prepare to work on top of <commit>, by detaching HEAD at it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.
-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching HEAD).--detachoption can be used to detach HEAD at the tip of the branch (gitcheckout-<branch> would check out that branch without detaching HEAD).-Omitting <branch> detaches HEAD at the tip of the current branch.
+Omitting <branch> detaches HEAD at the tip of the current branch.
- git checkout [-p|--patch] [<tree-ish>] [--] <pathspec>…
+- git checkout [-p|--patch] [<tree-ish>] [--] <pathspec>…
When <paths> or
--patchare given, git checkout does not switch branches. It updates the named paths in the working tree -from the index file or from a named <tree-ish> (most often a +from the index file or from a named <tree-ish> (most often a commit). In this case, the-band--trackoptions are meaningless and giving either of them results in an error. The -<tree-ish> argument can be used to specify a specific tree-ish +<tree-ish> argument can be used to specify a specific tree-ish (i.e. commit, tag or tree) to update the index for the given paths before updating the working tree.@@ -220,8 +220,8 @@@@ -61,25 +61,25 @@OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of "git checkout <commit>" when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior of "git checkout <commit>" when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.
- --orphan <new_branch>
@@ -294,16 +294,16 @@OPTIONS
- --patch
- -
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the “Interactive Mode” section of git-add[1] to learn how to operate the--patchmode.- <branch>
+- <branch>
- -
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -330,7 +330,7 @@
OPTIONS
The name of a commit at which to start the new branch; see git-branch[1] for details. Defaults to HEAD.
- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
diff --git a/external/docs/content/docs/git-checkout/2.10.5.html b/external/docs/content/docs/git-checkout/2.10.5.html index 23f1ef19a5..4885e7248d 100644 --- a/external/docs/content/docs/git-checkout/2.10.5.html +++ b/external/docs/content/docs/git-checkout/2.10.5.html @@ -41,12 +41,12 @@NAME
SYNOPSIS
-git checkout [-q] [-f] [-m] [<branch>] -git checkout [-q] [-f] [-m] --detach [<branch>] -git checkout [-q] [-f] [-m] [--detach] <commit> +git checkout [-q] [-f] [-m] [<branch>] +git checkout [-q] [-f] [-m] --detach [<branch>] +git checkout [-q] [-f] [-m] [--detach] <commit> git checkout [-q] [-f] [-m] [[-b|-B|--orphan] <new_branch>] [<start_point>] -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <paths>… -git checkout [-p|--patch] [<tree-ish>] [--] [<paths>…]+git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <paths>… +git checkout [-p|--patch] [<tree-ish>] [--] [<paths>…]DESCRIPTION
-
- git checkout <branch>
+- git checkout <branch>
- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing HEAD at the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.
+<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>-You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with a rather expensive side-effects to show only the tracking information, if exists, for the current branch.
@@ -99,8 +99,8 @@DESCRIPTION
--$ git branch -f <branch> [<start point>] -$ git checkout <branch>+$ git branch -f <branch> [<start point>] +$ git checkout <branch>- git checkout --detach [<branch>]
-- git checkout [--detach] <commit>
+- git checkout --detach [<branch>]
+- git checkout [--detach] <commit>
- -
-Prepare to work on top of <commit>, by detaching HEAD at it +
Prepare to work on top of <commit>, by detaching HEAD at it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.
-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching HEAD).--detachoption can be used to detach HEAD at the tip of the branch (gitcheckout-<branch> would check out that branch without detaching HEAD).-Omitting <branch> detaches HEAD at the tip of the current branch.
+Omitting <branch> detaches HEAD at the tip of the current branch.
- git checkout [-p|--patch] [<tree-ish>] [--] <pathspec>…
+- git checkout [-p|--patch] [<tree-ish>] [--] <pathspec>…
When <paths> or
--patchare given, git checkout does not switch branches. It updates the named paths in the working tree -from the index file or from a named <tree-ish> (most often a +from the index file or from a named <tree-ish> (most often a commit). In this case, the-band--trackoptions are meaningless and giving either of them results in an error. The -<tree-ish> argument can be used to specify a specific tree-ish +<tree-ish> argument can be used to specify a specific tree-ish (i.e. commit, tag or tree) to update the index for the given paths before updating the working tree.git checkout with <paths> or
+with the contents from a named <tree-ish> (most often a commit-ish).--patchis used to restore modified or deleted paths to their original contents from the index or replace paths -with the contents from a named <tree-ish> (most often a commit-ish).@@ -59,25 +59,25 @@The index may contain unmerged entries because of a previous failed merge. @@ -250,8 +250,8 @@
OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of "git checkout <commit>" when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior of "git checkout <commit>" when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.
- --orphan <new_branch>
@@ -324,9 +324,9 @@OPTIONS
- --patch
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).diff --git a/external/docs/content/docs/git-checkout/2.13.7.html b/external/docs/content/docs/git-checkout/2.13.7.html index 88aa4a5c25..b600eb44a7 100644 --- a/external/docs/content/docs/git-checkout/2.13.7.html +++ b/external/docs/content/docs/git-checkout/2.13.7.html @@ -39,12 +39,12 @@This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the “Interactive Mode” @@ -340,7 +340,7 @@OPTIONS
out anyway. In other words, the ref can be held by more than one worktree. -- <branch>
+- <branch>
- -
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -367,7 +367,7 @@
OPTIONS
The name of a commit at which to start the new branch; see git-branch[1] for details. Defaults to HEAD.
- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
@@ -542,12 +542,12 @@
When there is only one argument given and it is not
--(e.g. "git -checkout abc"), and when the argument is both a valid <tree-ish> -(e.g. a branch "abc" exists) and a valid <pathspec> (e.g. a file +checkout abc"), and when the argument is both a valid <tree-ish> +(e.g. a branch "abc" exists) and a valid <pathspec> (e.g. a file or a directory whose name is "abc" exists), Git would usually ask you to disambiguate. Because checking out a branch is so common an -operation, however, "git checkout abc" takes "abc" as a <tree-ish> -in such a situation. Usegitcheckout--<pathspec> if you want +operation, however, "git checkout abc" takes "abc" as a <tree-ish> +in such a situation. Usegitcheckout--<pathspec> if you want to checkout these paths out of the index.NAME
SYNOPSIS
-git checkout [-q] [-f] [-m] [<branch>] -git checkout [-q] [-f] [-m] --detach [<branch>] -git checkout [-q] [-f] [-m] [--detach] <commit> +git checkout [-q] [-f] [-m] [<branch>] +git checkout [-q] [-f] [-m] --detach [<branch>] +git checkout [-q] [-f] [-m] [--detach] <commit> git checkout [-q] [-f] [-m] [[-b|-B|--orphan] <new_branch>] [<start_point>] -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <paths>… -git checkout [-p|--patch] [<tree-ish>] [--] [<paths>…]+git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <paths>… +git checkout [-p|--patch] [<tree-ish>] [--] [<paths>…]DESCRIPTION
-
- git checkout <branch>
+- git checkout <branch>
- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing HEAD at the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.
+<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>-You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with a rather expensive side-effects to show only the tracking information, if exists, for the current branch.
@@ -97,8 +97,8 @@DESCRIPTION
--$ git branch -f <branch> [<start point>] -$ git checkout <branch>+$ git branch -f <branch> [<start point>] +$ git checkout <branch>- git checkout --detach [<branch>]
-- git checkout [--detach] <commit>
+- git checkout --detach [<branch>]
+- git checkout [--detach] <commit>
- -
-Prepare to work on top of <commit>, by detaching HEAD at it +
Prepare to work on top of <commit>, by detaching HEAD at it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.
-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching HEAD).--detachoption can be used to detach HEAD at the tip of the branch (gitcheckout-<branch> would check out that branch without detaching HEAD).-Omitting <branch> detaches HEAD at the tip of the current branch.
+Omitting <branch> detaches HEAD at the tip of the current branch.
- git checkout [-p|--patch] [<tree-ish>] [--] <pathspec>…
+- git checkout [-p|--patch] [<tree-ish>] [--] <pathspec>…
When <paths> or
--patchare given, git checkout does not switch branches. It updates the named paths in the working tree -from the index file or from a named <tree-ish> (most often a +from the index file or from a named <tree-ish> (most often a commit). In this case, the-band--trackoptions are meaningless and giving either of them results in an error. The -<tree-ish> argument can be used to specify a specific tree-ish +<tree-ish> argument can be used to specify a specific tree-ish (i.e. commit, tag or tree) to update the index for the given paths before updating the working tree.git checkout with <paths> or
+with the contents from a named <tree-ish> (most often a commit-ish).--patchis used to restore modified or deleted paths to their original contents from the index or replace paths -with the contents from a named <tree-ish> (most often a commit-ish).@@ -61,25 +61,25 @@The index may contain unmerged entries because of a previous failed merge. @@ -248,8 +248,8 @@
OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of "git checkout <commit>" when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior of "git checkout <commit>" when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.
- --orphan <new_branch>
@@ -322,9 +322,9 @@OPTIONS
- --patch
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).diff --git a/external/docs/content/docs/git-checkout/2.14.6.html b/external/docs/content/docs/git-checkout/2.14.6.html index ed8f6850f8..21baf8e0c6 100644 --- a/external/docs/content/docs/git-checkout/2.14.6.html +++ b/external/docs/content/docs/git-checkout/2.14.6.html @@ -40,13 +40,13 @@This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the “Interactive Mode” @@ -346,7 +346,7 @@OPTIONS
will fail unless-fis used. If nothing (or --no-recurse-submodules) is used, the work trees of submodules will not be updated. -- <branch>
+- <branch>
- -
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -373,7 +373,7 @@
OPTIONS
The name of a commit at which to start the new branch; see git-branch[1] for details. Defaults to HEAD.
- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
@@ -548,12 +548,12 @@
When there is only one argument given and it is not
--(e.g. "git -checkout abc"), and when the argument is both a valid <tree-ish> -(e.g. a branch "abc" exists) and a valid <pathspec> (e.g. a file +checkout abc"), and when the argument is both a valid <tree-ish> +(e.g. a branch "abc" exists) and a valid <pathspec> (e.g. a file or a directory whose name is "abc" exists), Git would usually ask you to disambiguate. Because checking out a branch is so common an -operation, however, "git checkout abc" takes "abc" as a <tree-ish> -in such a situation. Usegitcheckout--<pathspec> if you want +operation, however, "git checkout abc" takes "abc" as a <tree-ish> +in such a situation. Usegitcheckout--<pathspec> if you want to checkout these paths out of the index.NAME
SYNOPSIS
-git checkout [-q] [-f] [-m] [<branch>] -git checkout [-q] [-f] [-m] --detach [<branch>] -git checkout [-q] [-f] [-m] [--detach] <commit> +git checkout [-q] [-f] [-m] [<branch>] +git checkout [-q] [-f] [-m] --detach [<branch>] +git checkout [-q] [-f] [-m] [--detach] <commit> git checkout [-q] [-f] [-m] [[-b|-B|--orphan] <new_branch>] [<start_point>] -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <paths>… -git checkout [<tree-ish>] [--] <pathspec>… -git checkout (-p|--patch) [<tree-ish>] [--] [<paths>…]+git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <paths>… +git checkout [<tree-ish>] [--] <pathspec>… +git checkout (-p|--patch) [<tree-ish>] [--] [<paths>…]DESCRIPTION
-
- git checkout <branch>
+- git checkout <branch>
- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing HEAD at the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.
+<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>-@@ -73,25 +73,25 @@You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with rather expensive side-effects to show only the tracking information, if exists, for the current branch.
@@ -99,8 +99,8 @@DESCRIPTION
--$ git branch -f <branch> [<start point>] -$ git checkout <branch>+$ git branch -f <branch> [<start point>] +$ git checkout <branch>- git checkout --detach [<branch>]
-- git checkout [--detach] <commit>
+- git checkout --detach [<branch>]
+- git checkout [--detach] <commit>
- -
-Prepare to work on top of <commit>, by detaching HEAD at it +
Prepare to work on top of <commit>, by detaching HEAD at it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.
-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching HEAD).--detachoption can be used to detach HEAD at the tip of the branch (gitcheckout-<branch> would check out that branch without detaching HEAD).-Omitting <branch> detaches HEAD at the tip of the current branch.
+Omitting <branch> detaches HEAD at the tip of the current branch.
- git checkout [<tree-ish>] [--] <pathspec>…
+- git checkout [<tree-ish>] [--] <pathspec>…
- -
Overwrite paths in the working tree by replacing with the -contents in the index or in the <tree-ish> (most often a -commit). When a <tree-ish> is given, the paths that -match the <pathspec> are updated both in the index and in +contents in the index or in the <tree-ish> (most often a +commit). When a <tree-ish> is given, the paths that +match the <pathspec> are updated both in the index and in the working tree.
- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
+- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
This is similar to the "check out paths to the working tree from either the index or from a tree-ish" mode described @@ -250,8 +250,8 @@
OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of "git checkout <commit>" when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior of "git checkout <commit>" when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.
- --orphan <new_branch>
@@ -324,9 +324,9 @@OPTIONS
- --patch
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).diff --git a/external/docs/content/docs/git-checkout/2.16.6.html b/external/docs/content/docs/git-checkout/2.16.6.html index 69fb180191..65841c08a3 100644 --- a/external/docs/content/docs/git-checkout/2.16.6.html +++ b/external/docs/content/docs/git-checkout/2.16.6.html @@ -52,13 +52,13 @@This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the “Interactive Mode” @@ -348,7 +348,7 @@OPTIONS
will fail unless-fis used. If nothing (or --no-recurse-submodules) is used, the work trees of submodules will not be updated. -- <branch>
+- <branch>
- -
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -375,7 +375,7 @@
OPTIONS
The name of a commit at which to start the new branch; see git-branch[1] for details. Defaults to HEAD.
- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
@@ -550,12 +550,12 @@
When there is only one argument given and it is not
--(e.g. "git -checkout abc"), and when the argument is both a valid <tree-ish> -(e.g. a branch "abc" exists) and a valid <pathspec> (e.g. a file +checkout abc"), and when the argument is both a valid <tree-ish> +(e.g. a branch "abc" exists) and a valid <pathspec> (e.g. a file or a directory whose name is "abc" exists), Git would usually ask you to disambiguate. Because checking out a branch is so common an -operation, however, "git checkout abc" takes "abc" as a <tree-ish> -in such a situation. Usegitcheckout--<pathspec> if you want +operation, however, "git checkout abc" takes "abc" as a <tree-ish> +in such a situation. Usegitcheckout--<pathspec> if you want to checkout these paths out of the index.NAME
SYNOPSIS
-git checkout [-q] [-f] [-m] [<branch>] -git checkout [-q] [-f] [-m] --detach [<branch>] -git checkout [-q] [-f] [-m] [--detach] <commit> +git checkout [-q] [-f] [-m] [<branch>] +git checkout [-q] [-f] [-m] --detach [<branch>] +git checkout [-q] [-f] [-m] [--detach] <commit> git checkout [-q] [-f] [-m] [[-b|-B|--orphan] <new_branch>] [<start_point>] -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <paths>… -git checkout [<tree-ish>] [--] <pathspec>… -git checkout (-p|--patch) [<tree-ish>] [--] [<paths>…]+git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <paths>… +git checkout [<tree-ish>] [--] <pathspec>… +git checkout (-p|--patch) [<tree-ish>] [--] [<paths>…]DESCRIPTION
-
- git checkout <branch>
+- git checkout <branch>
- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing HEAD at the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.
+<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>-@@ -61,35 +61,35 @@You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with rather expensive side-effects to show only the tracking information, if exists, for the current branch.
@@ -111,8 +111,8 @@DESCRIPTION
--$ git branch -f <branch> [<start point>] -$ git checkout <branch>+$ git branch -f <branch> [<start point>] +$ git checkout <branch>- git checkout --detach [<branch>]
-- git checkout [--detach] <commit>
+- git checkout --detach [<branch>]
+- git checkout [--detach] <commit>
- -
-Prepare to work on top of <commit>, by detaching HEAD at it +
Prepare to work on top of <commit>, by detaching HEAD at it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.
-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching HEAD).--detachoption can be used to detach HEAD at the tip of the branch (gitcheckout-<branch> would check out that branch without detaching HEAD).-Omitting <branch> detaches HEAD at the tip of the current branch.
+Omitting <branch> detaches HEAD at the tip of the current branch.
- git checkout [<tree-ish>] [--] <pathspec>…
+- git checkout [<tree-ish>] [--] <pathspec>…
- -
Overwrite paths in the working tree by replacing with the -contents in the index or in the <tree-ish> (most often a -commit). When a <tree-ish> is given, the paths that -match the <pathspec> are updated both in the index and in +contents in the index or in the <tree-ish> (most often a +commit). When a <tree-ish> is given, the paths that +match the <pathspec> are updated both in the index and in the working tree.
- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
+- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
This is similar to the "check out paths to the working tree from either the index or from a tree-ish" mode described @@ -262,8 +262,8 @@
OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of "git checkout <commit>" when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior of "git checkout <commit>" when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.
- --orphan <new_branch>
@@ -336,9 +336,9 @@OPTIONS
- --patch
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).diff --git a/external/docs/content/docs/git-checkout/2.19.0.html b/external/docs/content/docs/git-checkout/2.19.0.html index b5ab4028ea..a60e65d964 100644 --- a/external/docs/content/docs/git-checkout/2.19.0.html +++ b/external/docs/content/docs/git-checkout/2.19.0.html @@ -40,13 +40,13 @@This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the “Interactive Mode” @@ -362,7 +362,7 @@OPTIONS
Just like git-submodule[1], this will detach the submodules HEAD. -- <branch>
+- <branch>
- -
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -389,7 +389,7 @@
OPTIONS
The name of a commit at which to start the new branch; see git-branch[1] for details. Defaults to HEAD.
- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
@@ -564,12 +564,12 @@
When there is only one argument given and it is not
--(e.g. "git -checkout abc"), and when the argument is both a valid <tree-ish> -(e.g. a branch "abc" exists) and a valid <pathspec> (e.g. a file +checkout abc"), and when the argument is both a valid <tree-ish> +(e.g. a branch "abc" exists) and a valid <pathspec> (e.g. a file or a directory whose name is "abc" exists), Git would usually ask you to disambiguate. Because checking out a branch is so common an -operation, however, "git checkout abc" takes "abc" as a <tree-ish> -in such a situation. Usegitcheckout--<pathspec> if you want +operation, however, "git checkout abc" takes "abc" as a <tree-ish> +in such a situation. Usegitcheckout--<pathspec> if you want to checkout these paths out of the index.NAME
SYNOPSIS
-git checkout [-q] [-f] [-m] [<branch>] -git checkout [-q] [-f] [-m] --detach [<branch>] -git checkout [-q] [-f] [-m] [--detach] <commit> +git checkout [-q] [-f] [-m] [<branch>] +git checkout [-q] [-f] [-m] --detach [<branch>] +git checkout [-q] [-f] [-m] [--detach] <commit> git checkout [-q] [-f] [-m] [[-b|-B|--orphan] <new_branch>] [<start_point>] -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <paths>… -git checkout [<tree-ish>] [--] <pathspec>… -git checkout (-p|--patch) [<tree-ish>] [--] [<paths>…]+git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <paths>… +git checkout [<tree-ish>] [--] <pathspec>… +git checkout (-p|--patch) [<tree-ish>] [--] [<paths>…]DESCRIPTION
-
- git checkout <branch>
+- git checkout <branch>
- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing HEAD at the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.
+<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>If the branch exists in multiple remotes and one of them is named by the
checkout.defaultRemoteconfiguration variable, we’ll use that -one for the purposes of disambiguation, even if the <branch> isn’t +one for the purposes of disambiguation, even if the <branch> isn’t unique across all remotes. Set it to e.g.checkout.defaultRemote=originto always checkout remote -branches from there if <branch> is ambiguous but exists on the +branches from there if <branch> is ambiguous but exists on the origin remote. See alsocheckout.defaultRemotein git-config[1].-@@ -70,35 +70,35 @@You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with rather expensive side-effects to show only the tracking information, if exists, for the current branch.
@@ -109,8 +109,8 @@DESCRIPTION
--$ git branch -f <branch> [<start point>] -$ git checkout <branch>+$ git branch -f <branch> [<start point>] +$ git checkout <branch>- git checkout --detach [<branch>]
-- git checkout [--detach] <commit>
+- git checkout --detach [<branch>]
+- git checkout [--detach] <commit>
- -
-Prepare to work on top of <commit>, by detaching HEAD at it +
Prepare to work on top of <commit>, by detaching HEAD at it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.
-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching HEAD).--detachoption can be used to detach HEAD at the tip of the branch (gitcheckout-<branch> would check out that branch without detaching HEAD).-Omitting <branch> detaches HEAD at the tip of the current branch.
+Omitting <branch> detaches HEAD at the tip of the current branch.
- git checkout [<tree-ish>] [--] <pathspec>…
+- git checkout [<tree-ish>] [--] <pathspec>…
- -
Overwrite paths in the working tree by replacing with the -contents in the index or in the <tree-ish> (most often a -commit). When a <tree-ish> is given, the paths that -match the <pathspec> are updated both in the index and in +contents in the index or in the <tree-ish> (most often a +commit). When a <tree-ish> is given, the paths that +match the <pathspec> are updated both in the index and in the working tree.
- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
+- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
This is similar to the "check out paths to the working tree from either the index or from a tree-ish" mode described @@ -260,8 +260,8 @@
OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of "git checkout <commit>" when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior of "git checkout <commit>" when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.
- --orphan <new_branch>
@@ -334,9 +334,9 @@OPTIONS
- --patch
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).diff --git a/external/docs/content/docs/git-checkout/2.19.2.html b/external/docs/content/docs/git-checkout/2.19.2.html index dc5252e2cb..72ea8a33c6 100644 --- a/external/docs/content/docs/git-checkout/2.19.2.html +++ b/external/docs/content/docs/git-checkout/2.19.2.html @@ -49,13 +49,13 @@This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the “Interactive Mode” @@ -360,7 +360,7 @@OPTIONS
Just like git-submodule[1], this will detach the submodules HEAD. -- <branch>
+- <branch>
- -
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -387,7 +387,7 @@
OPTIONS
The name of a commit at which to start the new branch; see git-branch[1] for details. Defaults to HEAD.
- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
@@ -562,12 +562,12 @@
When there is only one argument given and it is not
--(e.g. "git -checkout abc"), and when the argument is both a valid <tree-ish> -(e.g. a branch "abc" exists) and a valid <pathspec> (e.g. a file +checkout abc"), and when the argument is both a valid <tree-ish> +(e.g. a branch "abc" exists) and a valid <pathspec> (e.g. a file or a directory whose name is "abc" exists), Git would usually ask you to disambiguate. Because checking out a branch is so common an -operation, however, "git checkout abc" takes "abc" as a <tree-ish> -in such a situation. Usegitcheckout--<pathspec> if you want +operation, however, "git checkout abc" takes "abc" as a <tree-ish> +in such a situation. Usegitcheckout--<pathspec> if you want to checkout these paths out of the index.NAME
SYNOPSIS
-git checkout [-q] [-f] [-m] [<branch>] -git checkout [-q] [-f] [-m] --detach [<branch>] -git checkout [-q] [-f] [-m] [--detach] <commit> +git checkout [-q] [-f] [-m] [<branch>] +git checkout [-q] [-f] [-m] --detach [<branch>] +git checkout [-q] [-f] [-m] [--detach] <commit> git checkout [-q] [-f] [-m] [[-b|-B|--orphan] <new_branch>] [<start_point>] -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <paths>… -git checkout [<tree-ish>] [--] <pathspec>… -git checkout (-p|--patch) [<tree-ish>] [--] [<paths>…]+git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <paths>… +git checkout [<tree-ish>] [--] <pathspec>… +git checkout (-p|--patch) [<tree-ish>] [--] [<paths>…]DESCRIPTION
-
- git checkout <branch>
+- git checkout <branch>
- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing HEAD at the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.
+<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>If the branch exists in multiple remotes and one of them is named by the
checkout.defaultRemoteconfiguration variable, we’ll use that -one for the purposes of disambiguation, even if the <branch> isn’t +one for the purposes of disambiguation, even if the <branch> isn’t unique across all remotes. Set it to e.g.checkout.defaultRemote=originto always checkout remote -branches from there if <branch> is ambiguous but exists on the +branches from there if <branch> is ambiguous but exists on the origin remote. See alsocheckout.defaultRemotein git-config[1].-@@ -64,35 +64,35 @@You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with rather expensive side-effects to show only the tracking information, if exists, for the current branch.
@@ -118,8 +118,8 @@DESCRIPTION
--$ git branch -f <branch> [<start point>] -$ git checkout <branch>+$ git branch -f <branch> [<start point>] +$ git checkout <branch>- git checkout --detach [<branch>]
-- git checkout [--detach] <commit>
+- git checkout --detach [<branch>]
+- git checkout [--detach] <commit>
- -
-Prepare to work on top of <commit>, by detaching HEAD at it +
Prepare to work on top of <commit>, by detaching HEAD at it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.
-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching HEAD).--detachoption can be used to detach HEAD at the tip of the branch (gitcheckout-<branch> would check out that branch without detaching HEAD).-Omitting <branch> detaches HEAD at the tip of the current branch.
+Omitting <branch> detaches HEAD at the tip of the current branch.
- git checkout [<tree-ish>] [--] <pathspec>…
+- git checkout [<tree-ish>] [--] <pathspec>…
- -
Overwrite paths in the working tree by replacing with the -contents in the index or in the <tree-ish> (most often a -commit). When a <tree-ish> is given, the paths that -match the <pathspec> are updated both in the index and in +contents in the index or in the <tree-ish> (most often a +commit). When a <tree-ish> is given, the paths that +match the <pathspec> are updated both in the index and in the working tree.
- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
+- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
This is similar to the "check out paths to the working tree from either the index or from a tree-ish" mode described @@ -269,8 +269,8 @@
OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of "git checkout <commit>" when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior of "git checkout <commit>" when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.
- --orphan <new_branch>
@@ -343,9 +343,9 @@OPTIONS
- --patch
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).diff --git a/external/docs/content/docs/git-checkout/2.21.0.html b/external/docs/content/docs/git-checkout/2.21.0.html index 6f84c9edd6..37fd00a160 100644 --- a/external/docs/content/docs/git-checkout/2.21.0.html +++ b/external/docs/content/docs/git-checkout/2.21.0.html @@ -43,13 +43,13 @@This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the “Interactive Mode” @@ -369,7 +369,7 @@OPTIONS
Just like git-submodule[1], this will detach the submodules HEAD. -- <branch>
+- <branch>
- -
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -396,7 +396,7 @@
OPTIONS
The name of a commit at which to start the new branch; see git-branch[1] for details. Defaults to HEAD.
- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
@@ -571,12 +571,12 @@
When there is only one argument given and it is not
--(e.g. "git -checkout abc"), and when the argument is both a valid <tree-ish> -(e.g. a branch "abc" exists) and a valid <pathspec> (e.g. a file +checkout abc"), and when the argument is both a valid <tree-ish> +(e.g. a branch "abc" exists) and a valid <pathspec> (e.g. a file or a directory whose name is "abc" exists), Git would usually ask you to disambiguate. Because checking out a branch is so common an -operation, however, "git checkout abc" takes "abc" as a <tree-ish> -in such a situation. Usegitcheckout--<pathspec> if you want +operation, however, "git checkout abc" takes "abc" as a <tree-ish> +in such a situation. Usegitcheckout--<pathspec> if you want to checkout these paths out of the index.NAME
SYNOPSIS
-git checkout [-q] [-f] [-m] [<branch>] -git checkout [-q] [-f] [-m] --detach [<branch>] -git checkout [-q] [-f] [-m] [--detach] <commit> +git checkout [-q] [-f] [-m] [<branch>] +git checkout [-q] [-f] [-m] --detach [<branch>] +git checkout [-q] [-f] [-m] [--detach] <commit> git checkout [-q] [-f] [-m] [[-b|-B|--orphan] <new_branch>] [<start_point>] -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <paths>… -git checkout [<tree-ish>] [--] <pathspec>… -git checkout (-p|--patch) [<tree-ish>] [--] [<paths>…]+git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <paths>… +git checkout [<tree-ish>] [--] <pathspec>… +git checkout (-p|--patch) [<tree-ish>] [--] [<paths>…]DESCRIPTION
@@ -71,25 +71,25 @@-
- git checkout <branch>
+- git checkout <branch>
- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing HEAD at the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.
+<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>If the branch exists in multiple remotes and one of them is named by the
checkout.defaultRemoteconfiguration variable, we’ll use that -one for the purposes of disambiguation, even if the <branch> isn’t +one for the purposes of disambiguation, even if the <branch> isn’t unique across all remotes. Set it to e.g.checkout.defaultRemote=originto always checkout remote -branches from there if <branch> is ambiguous but exists on the +branches from there if <branch> is ambiguous but exists on the origin remote. See alsocheckout.defaultRemotein git-config[1].-@@ -65,35 +65,35 @@You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with rather expensive side-effects to show only the tracking information, if exists, for the current branch.
@@ -112,8 +112,8 @@DESCRIPTION
--$ git branch -f <branch> [<start point>] -$ git checkout <branch>+$ git branch -f <branch> [<start point>] +$ git checkout <branch>- git checkout --detach [<branch>]
-- git checkout [--detach] <commit>
+- git checkout --detach [<branch>]
+- git checkout [--detach] <commit>
- -
-Prepare to work on top of <commit>, by detaching HEAD at it +
Prepare to work on top of <commit>, by detaching HEAD at it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.
-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching HEAD).--detachoption can be used to detach HEAD at the tip of the branch (gitcheckout-<branch> would check out that branch without detaching HEAD).-Omitting <branch> detaches HEAD at the tip of the current branch.
+Omitting <branch> detaches HEAD at the tip of the current branch.
- git checkout [<tree-ish>] [--] <pathspec>…
+- git checkout [<tree-ish>] [--] <pathspec>…
- -
Overwrite paths in the working tree by replacing with the -contents in the index or in the <tree-ish> (most often a -commit). When a <tree-ish> is given, the paths that -match the <pathspec> are updated both in the index and in +contents in the index or in the <tree-ish> (most often a +commit). When a <tree-ish> is given, the paths that +match the <pathspec> are updated both in the index and in the working tree.
- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
+- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
This is similar to the "check out paths to the working tree from either the index or from a tree-ish" mode described @@ -263,8 +263,8 @@
OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of "git checkout <commit>" when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior of "git checkout <commit>" when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.
- --orphan <new_branch>
@@ -337,9 +337,9 @@OPTIONS
- --patch
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).diff --git a/external/docs/content/docs/git-checkout/2.22.0.html b/external/docs/content/docs/git-checkout/2.22.0.html index 47a2050e30..e59655d3d3 100644 --- a/external/docs/content/docs/git-checkout/2.22.0.html +++ b/external/docs/content/docs/git-checkout/2.22.0.html @@ -44,13 +44,13 @@This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the “Interactive Mode” @@ -368,7 +368,7 @@OPTIONS
Do not attempt to create a branch if a remote tracking branch of the same name exists.
-- <branch>
+- <branch>
- -
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -395,7 +395,7 @@
OPTIONS
The name of a commit at which to start the new branch; see git-branch[1] for details. Defaults to HEAD.
- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
@@ -570,12 +570,12 @@
When there is only one argument given and it is not
--(e.g. "git -checkout abc"), and when the argument is both a valid <tree-ish> -(e.g. a branch "abc" exists) and a valid <pathspec> (e.g. a file +checkout abc"), and when the argument is both a valid <tree-ish> +(e.g. a branch "abc" exists) and a valid <pathspec> (e.g. a file or a directory whose name is "abc" exists), Git would usually ask you to disambiguate. Because checking out a branch is so common an -operation, however, "git checkout abc" takes "abc" as a <tree-ish> -in such a situation. Usegitcheckout--<pathspec> if you want +operation, however, "git checkout abc" takes "abc" as a <tree-ish> +in such a situation. Usegitcheckout--<pathspec> if you want to checkout these paths out of the index.NAME
SYNOPSIS
-git checkout [-q] [-f] [-m] [<branch>] -git checkout [-q] [-f] [-m] --detach [<branch>] -git checkout [-q] [-f] [-m] [--detach] <commit> +git checkout [-q] [-f] [-m] [<branch>] +git checkout [-q] [-f] [-m] --detach [<branch>] +git checkout [-q] [-f] [-m] [--detach] <commit> git checkout [-q] [-f] [-m] [[-b|-B|--orphan] <new_branch>] [<start_point>] -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <paths>… -git checkout [<tree-ish>] [--] <pathspec>… -git checkout (-p|--patch) [<tree-ish>] [--] [<paths>…]+git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <paths>… +git checkout [<tree-ish>] [--] <pathspec>… +git checkout (-p|--patch) [<tree-ish>] [--] [<paths>…]DESCRIPTION
@@ -71,25 +71,25 @@-
- git checkout <branch>
+- git checkout <branch>
- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing HEAD at the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.
+<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>If the branch exists in multiple remotes and one of them is named by the
checkout.defaultRemoteconfiguration variable, we’ll use that -one for the purposes of disambiguation, even if the <branch> isn’t +one for the purposes of disambiguation, even if the <branch> isn’t unique across all remotes. Set it to e.g.checkout.defaultRemote=originto always checkout remote -branches from there if <branch> is ambiguous but exists on the +branches from there if <branch> is ambiguous but exists on the origin remote. See alsocheckout.defaultRemotein git-config[1].-diff --git a/external/docs/content/docs/git-checkout/2.23.0.html b/external/docs/content/docs/git-checkout/2.23.0.html index d34a3ba687..0984b46f05 100644 --- a/external/docs/content/docs/git-checkout/2.23.0.html +++ b/external/docs/content/docs/git-checkout/2.23.0.html @@ -50,13 +50,13 @@You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with rather expensive side-effects to show only the tracking information, if exists, for the current branch.
@@ -113,8 +113,8 @@DESCRIPTION
--$ git branch -f <branch> [<start point>] -$ git checkout <branch>+$ git branch -f <branch> [<start point>] +$ git checkout <branch>- git checkout --detach [<branch>]
-- git checkout [--detach] <commit>
+- git checkout --detach [<branch>]
+- git checkout [--detach] <commit>
- -
-Prepare to work on top of <commit>, by detaching HEAD at it +
Prepare to work on top of <commit>, by detaching HEAD at it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.
-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching HEAD).--detachoption can be used to detach HEAD at the tip of the branch (gitcheckout-<branch> would check out that branch without detaching HEAD).-Omitting <branch> detaches HEAD at the tip of the current branch.
+Omitting <branch> detaches HEAD at the tip of the current branch.
- git checkout [<tree-ish>] [--] <pathspec>…
+- git checkout [<tree-ish>] [--] <pathspec>…
- -
Overwrite paths in the working tree by replacing with the -contents in the index or in the <tree-ish> (most often a -commit). When a <tree-ish> is given, the paths that -match the <pathspec> are updated both in the index and in +contents in the index or in the <tree-ish> (most often a +commit). When a <tree-ish> is given, the paths that +match the <pathspec> are updated both in the index and in the working tree.
- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
+- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
This is similar to the "check out paths to the working tree from either the index or from a tree-ish" mode described @@ -264,8 +264,8 @@
OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of "git checkout <commit>" when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior of "git checkout <commit>" when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.
- --orphan <new_branch>
@@ -341,9 +341,9 @@OPTIONS
- --patch
- -
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the “Interactive Mode” @@ -381,10 +381,10 @@OPTIONS
In the default overlay mode,
+working tree, but not in <tree-ish> are removed, to make them +match <tree-ish> exactly. -gitcheckoutnever removes files from the index or the working tree. When specifying--no-overlay, files that appear in the index and -working tree, but not in <tree-ish> are removed, to make them -match <tree-ish> exactly.- <branch>
+- <branch>
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -416,7 +416,7 @@
OPTIONS
leave out at most one ofAandB, in which case it defaults toHEAD.- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
@@ -591,12 +591,12 @@
When there is only one argument given and it is not
--(e.g. "git -checkout abc"), and when the argument is both a valid <tree-ish> -(e.g. a branch "abc" exists) and a valid <pathspec> (e.g. a file +checkout abc"), and when the argument is both a valid <tree-ish> +(e.g. a branch "abc" exists) and a valid <pathspec> (e.g. a file or a directory whose name is "abc" exists), Git would usually ask you to disambiguate. Because checking out a branch is so common an -operation, however, "git checkout abc" takes "abc" as a <tree-ish> -in such a situation. Usegitcheckout--<pathspec> if you want +operation, however, "git checkout abc" takes "abc" as a <tree-ish> +in such a situation. Usegitcheckout--<pathspec> if you want to checkout these paths out of the index.NAME
SYNOPSIS
-git checkout [-q] [-f] [-m] [<branch>] -git checkout [-q] [-f] [-m] --detach [<branch>] -git checkout [-q] [-f] [-m] [--detach] <commit> +git checkout [-q] [-f] [-m] [<branch>] +git checkout [-q] [-f] [-m] --detach [<branch>] +git checkout [-q] [-f] [-m] [--detach] <commit> git checkout [-q] [-f] [-m] [[-b|-B|--orphan] <new_branch>] [<start_point>] -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <paths>… -git checkout [<tree-ish>] [--] <pathspec>… -git checkout (-p|--patch) [<tree-ish>] [--] [<paths>…]+git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <paths>… +git checkout [<tree-ish>] [--] <pathspec>… +git checkout (-p|--patch) [<tree-ish>] [--] [<paths>…]DESCRIPTION
diff --git a/external/docs/content/docs/git-checkout/2.25.0.html b/external/docs/content/docs/git-checkout/2.25.0.html index c5ba3c54f6..c957158073 100644 --- a/external/docs/content/docs/git-checkout/2.25.0.html +++ b/external/docs/content/docs/git-checkout/2.25.0.html @@ -50,13 +50,13 @@-
- git checkout [<branch>]
+- git checkout [<branch>]
- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing
+<branch>.HEADat the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name and
--no-guessis not specified, treat as equivalent to-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>-You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with rather expensive side-effects to show only the tracking information, if exists, for the current branch.
@@ -109,8 +109,8 @@DESCRIPTION
--$ git branch -f <branch> [<start point>] -$ git checkout <branch>+$ git branch -f <branch> [<start point>] +$ git checkout <branch>- git checkout --detach [<branch>]
-- git checkout [--detach] <commit>
+- git checkout --detach [<branch>]
+- git checkout [--detach] <commit>
- -
-Prepare to work on top of <commit>, by detaching
HEADat it +Prepare to work on top of <commit>, by detaching
HEADat it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching--detachoption can be used to detachHEADat the tip of the branch (gitcheckout-<branch> would check out that branch without detachingHEAD).HEAD).-Omitting <branch> detaches
+HEADat the tip of the current branch.Omitting <branch> detaches
HEADat the tip of the current branch.- git checkout [<tree-ish>] [--] <pathspec>…
+- git checkout [<tree-ish>] [--] <pathspec>…
- -
Overwrite paths in the working tree by replacing with the -contents in the index or in the <tree-ish> (most often a -commit). When a <tree-ish> is given, the paths that -match the <pathspec> are updated both in the index and in +contents in the index or in the <tree-ish> (most often a +commit). When a <tree-ish> is given, the paths that +match the <pathspec> are updated both in the index and in the working tree.
- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
+- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
This is similar to the "check out paths to the working tree from either the index or from a tree-ish" mode described @@ -255,21 +255,21 @@
OPTIONS
- --guess
- --no-guess
- -
If <branch> is not found but there does exist a tracking +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>@@ -286,8 +286,8 @@If the branch exists in multiple remotes and one of them is named by the
checkout.defaultRemoteconfiguration variable, we’ll use that -one for the purposes of disambiguation, even if the <branch> isn’t +one for the purposes of disambiguation, even if the <branch> isn’t unique across all remotes. Set it to e.g.checkout.defaultRemote=originto always checkout remote -branches from there if <branch> is ambiguous but exists on the +branches from there if <branch> is ambiguous but exists on the origin remote. See alsocheckout.defaultRemotein git-config[1].OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of
gitcheckout<commit> when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior ofgitcheckout<commit> when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.- --orphan <new_branch>
@@ -363,9 +363,9 @@OPTIONS
- --patch
- -
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the “Interactive Mode” @@ -407,10 +407,10 @@OPTIONS
In the default overlay mode,
+working tree, but not in <tree-ish> are removed, to make them +match <tree-ish> exactly. -gitcheckoutnever removes files from the index or the working tree. When specifying--no-overlay, files that appear in the index and -working tree, but not in <tree-ish> are removed, to make them -match <tree-ish> exactly.- <branch>
+- <branch>
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -442,7 +442,7 @@
OPTIONS
leave out at most one ofAandB, in which case it defaults toHEAD.- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
@@ -618,12 +618,12 @@
When there is only one argument given and it is not
--(e.g.git-checkoutabc), and when the argument is both a valid <tree-ish> -(e.g. a branchabcexists) and a valid <pathspec> (e.g. a file +checkoutabc), and when the argument is both a valid <tree-ish> +(e.g. a branchabcexists) and a valid <pathspec> (e.g. a file or a directory whose name is "abc" exists), Git would usually ask you to disambiguate. Because checking out a branch is so common an -operation, however,gitcheckoutabctakes "abc" as a <tree-ish> -in such a situation. Usegitcheckout--<pathspec> if you want +operation, however,gitcheckoutabctakes "abc" as a <tree-ish> +in such a situation. Usegitcheckout--<pathspec> if you want to checkout these paths out of the index.NAME
SYNOPSIS
-git checkout [-q] [-f] [-m] [<branch>] -git checkout [-q] [-f] [-m] --detach [<branch>] -git checkout [-q] [-f] [-m] [--detach] <commit> +git checkout [-q] [-f] [-m] [<branch>] +git checkout [-q] [-f] [-m] --detach [<branch>] +git checkout [-q] [-f] [-m] [--detach] <commit> git checkout [-q] [-f] [-m] [[-b|-B|--orphan] <new_branch>] [<start_point>] -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>… -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul] -git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]+git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>… +git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul] +git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]DESCRIPTION
@@ -65,25 +65,25 @@-
- git checkout [<branch>]
+- git checkout [<branch>]
- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing
+<branch>.HEADat the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name and
--no-guessis not specified, treat as equivalent to-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>-diff --git a/external/docs/content/docs/git-checkout/2.27.0.html b/external/docs/content/docs/git-checkout/2.27.0.html index 66884c09fa..46dfe0daf8 100644 --- a/external/docs/content/docs/git-checkout/2.27.0.html +++ b/external/docs/content/docs/git-checkout/2.27.0.html @@ -44,13 +44,13 @@You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with rather expensive side-effects to show only the tracking information, if exists, for the current branch.
@@ -109,8 +109,8 @@DESCRIPTION
--$ git branch -f <branch> [<start point>] -$ git checkout <branch>+$ git branch -f <branch> [<start point>] +$ git checkout <branch>- git checkout --detach [<branch>]
-- git checkout [--detach] <commit>
+- git checkout --detach [<branch>]
+- git checkout [--detach] <commit>
- -
-Prepare to work on top of <commit>, by detaching
HEADat it +Prepare to work on top of <commit>, by detaching
HEADat it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching--detachoption can be used to detachHEADat the tip of the branch (gitcheckout-<branch> would check out that branch without detachingHEAD).HEAD).-Omitting <branch> detaches
+HEADat the tip of the current branch.Omitting <branch> detaches
HEADat the tip of the current branch.- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
-- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
- -
Overwrite the contents of the files that match the pathspec. -When the <tree-ish> (most often a commit) is not given, +When the <tree-ish> (most often a commit) is not given, overwrite working tree with the contents in the index. -When the <tree-ish> is given, overwrite both the index and -the working tree with the contents at the <tree-ish>.
+When the <tree-ish> is given, overwrite both the index and +the working tree with the contents at the <tree-ish>.- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
+- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
This is similar to the previous mode, but lets you use the interactive interface to show the "diff" output and choose which @@ -255,21 +255,21 @@
OPTIONS
- --guess
- --no-guess
- -
If <branch> is not found but there does exist a tracking +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>@@ -286,8 +286,8 @@If the branch exists in multiple remotes and one of them is named by the
checkout.defaultRemoteconfiguration variable, we’ll use that -one for the purposes of disambiguation, even if the <branch> isn’t +one for the purposes of disambiguation, even if the <branch> isn’t unique across all remotes. Set it to e.g.checkout.defaultRemote=originto always checkout remote -branches from there if <branch> is ambiguous but exists on the +branches from there if <branch> is ambiguous but exists on the origin remote. See alsocheckout.defaultRemotein git-config[1].OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of
gitcheckout<commit> when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior ofgitcheckout<commit> when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.- --orphan <new_branch>
@@ -363,9 +363,9 @@OPTIONS
- --patch
- -
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the “Interactive Mode” @@ -407,8 +407,8 @@OPTIONS
In the default overlay mode,
+working tree, but not in <tree-ish> are removed, to make them +match <tree-ish> exactly.gitcheckoutnever removes files from the index or the working tree. When specifying--no-overlay, files that appear in the index and -working tree, but not in <tree-ish> are removed, to make them -match <tree-ish> exactly.- --pathspec-from-file=<file>
- @@ -425,7 +425,7 @@
-OPTIONS
separated with NUL character and all other characters are taken literally (including newlines and quotes).- <branch>
+- <branch>
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -457,7 +457,7 @@
OPTIONS
leave out at most one ofAandB, in which case it defaults toHEAD.- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
@@ -466,7 +466,7 @@OPTIONS
- -
Do not interpret any more arguments as options.
- <pathspec>…
+- <pathspec>…
Limits the paths affected by the operation.
NAME
SYNOPSIS
-git checkout [-q] [-f] [-m] [<branch>] -git checkout [-q] [-f] [-m] --detach [<branch>] -git checkout [-q] [-f] [-m] [--detach] <commit> +git checkout [-q] [-f] [-m] [<branch>] +git checkout [-q] [-f] [-m] --detach [<branch>] +git checkout [-q] [-f] [-m] [--detach] <commit> git checkout [-q] [-f] [-m] [[-b|-B|--orphan] <new_branch>] [<start_point>] -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>… -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul] -git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]+git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>… +git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul] +git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]DESCRIPTION
@@ -65,25 +65,25 @@-
- git checkout [<branch>]
+- git checkout [<branch>]
- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing
+<branch>.HEADat the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name and
--no-guessis not specified, treat as equivalent to-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>-diff --git a/external/docs/content/docs/git-checkout/2.29.0.html b/external/docs/content/docs/git-checkout/2.29.0.html index f44d74c84c..fbf323e66e 100644 --- a/external/docs/content/docs/git-checkout/2.29.0.html +++ b/external/docs/content/docs/git-checkout/2.29.0.html @@ -44,13 +44,13 @@You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with rather expensive side-effects to show only the tracking information, if exists, for the current branch.
@@ -103,8 +103,8 @@DESCRIPTION
--$ git branch -f <branch> [<start point>] -$ git checkout <branch>+$ git branch -f <branch> [<start point>] +$ git checkout <branch>- git checkout --detach [<branch>]
-- git checkout [--detach] <commit>
+- git checkout --detach [<branch>]
+- git checkout [--detach] <commit>
- -
-Prepare to work on top of <commit>, by detaching
HEADat it +Prepare to work on top of <commit>, by detaching
HEADat it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching--detachoption can be used to detachHEADat the tip of the branch (gitcheckout-<branch> would check out that branch without detachingHEAD).HEAD).-Omitting <branch> detaches
+HEADat the tip of the current branch.Omitting <branch> detaches
HEADat the tip of the current branch.- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
-- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
- -
Overwrite the contents of the files that match the pathspec. -When the <tree-ish> (most often a commit) is not given, +When the <tree-ish> (most often a commit) is not given, overwrite working tree with the contents in the index. -When the <tree-ish> is given, overwrite both the index and -the working tree with the contents at the <tree-ish>.
+When the <tree-ish> is given, overwrite both the index and +the working tree with the contents at the <tree-ish>.- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
+- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
This is similar to the previous mode, but lets you use the interactive interface to show the "diff" output and choose which @@ -249,21 +249,21 @@
OPTIONS
- --guess
- --no-guess
- -
If <branch> is not found but there does exist a tracking +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>@@ -280,8 +280,8 @@If the branch exists in multiple remotes and one of them is named by the
checkout.defaultRemoteconfiguration variable, we’ll use that -one for the purposes of disambiguation, even if the <branch> isn’t +one for the purposes of disambiguation, even if the <branch> isn’t unique across all remotes. Set it to e.g.checkout.defaultRemote=originto always checkout remote -branches from there if <branch> is ambiguous but exists on the +branches from there if <branch> is ambiguous but exists on the origin remote. See alsocheckout.defaultRemotein git-config[1].OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of
gitcheckout<commit> when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior ofgitcheckout<commit> when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.- --orphan <new_branch>
@@ -357,9 +357,9 @@OPTIONS
- --patch
- -
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the “Interactive Mode” @@ -401,8 +401,8 @@OPTIONS
In the default overlay mode,
+working tree, but not in <tree-ish> are removed, to make them +match <tree-ish> exactly.gitcheckoutnever removes files from the index or the working tree. When specifying--no-overlay, files that appear in the index and -working tree, but not in <tree-ish> are removed, to make them -match <tree-ish> exactly.- --pathspec-from-file=<file>
- @@ -419,7 +419,7 @@
-OPTIONS
separated with NUL character and all other characters are taken literally (including newlines and quotes).- <branch>
+- <branch>
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -451,7 +451,7 @@
OPTIONS
leave out at most one ofAandB, in which case it defaults toHEAD.- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
@@ -460,7 +460,7 @@OPTIONS
- -
Do not interpret any more arguments as options.
- <pathspec>…
+- <pathspec>…
Limits the paths affected by the operation.
NAME
SYNOPSIS
-git checkout [-q] [-f] [-m] [<branch>] -git checkout [-q] [-f] [-m] --detach [<branch>] -git checkout [-q] [-f] [-m] [--detach] <commit> +git checkout [-q] [-f] [-m] [<branch>] +git checkout [-q] [-f] [-m] --detach [<branch>] +git checkout [-q] [-f] [-m] [--detach] <commit> git checkout [-q] [-f] [-m] [[-b|-B|--orphan] <new_branch>] [<start_point>] -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>… -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul] -git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]+git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>… +git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul] +git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]DESCRIPTION
@@ -97,25 +97,25 @@-
- git checkout [<branch>]
+- git checkout [<branch>]
- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing
+<branch>.HEADat the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name and
--no-guessis not specified, treat as equivalent to-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>-diff --git a/external/docs/content/docs/git-checkout/2.30.0.html b/external/docs/content/docs/git-checkout/2.30.0.html index b4a4282727..2c7461ba2d 100644 --- a/external/docs/content/docs/git-checkout/2.30.0.html +++ b/external/docs/content/docs/git-checkout/2.30.0.html @@ -76,13 +76,13 @@You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with rather expensive side-effects to show only the tracking information, if exists, for the current branch.
@@ -103,8 +103,8 @@DESCRIPTION
--$ git branch -f <branch> [<start point>] -$ git checkout <branch>+$ git branch -f <branch> [<start point>] +$ git checkout <branch>- git checkout --detach [<branch>]
-- git checkout [--detach] <commit>
+- git checkout --detach [<branch>]
+- git checkout [--detach] <commit>
- -
-Prepare to work on top of <commit>, by detaching
HEADat it +Prepare to work on top of <commit>, by detaching
HEADat it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching--detachoption can be used to detachHEADat the tip of the branch (gitcheckout-<branch> would check out that branch without detachingHEAD).HEAD).-Omitting <branch> detaches
+HEADat the tip of the current branch.Omitting <branch> detaches
HEADat the tip of the current branch.- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
-- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
- -
Overwrite the contents of the files that match the pathspec. -When the <tree-ish> (most often a commit) is not given, +When the <tree-ish> (most often a commit) is not given, overwrite working tree with the contents in the index. -When the <tree-ish> is given, overwrite both the index and -the working tree with the contents at the <tree-ish>.
+When the <tree-ish> is given, overwrite both the index and +the working tree with the contents at the <tree-ish>.- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
+- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
This is similar to the previous mode, but lets you use the interactive interface to show the "diff" output and choose which @@ -249,21 +249,21 @@
OPTIONS
- --guess
- --no-guess
- -
If <branch> is not found but there does exist a tracking +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>@@ -281,8 +281,8 @@If the branch exists in multiple remotes and one of them is named by the
checkout.defaultRemoteconfiguration variable, we’ll use that -one for the purposes of disambiguation, even if the <branch> isn’t +one for the purposes of disambiguation, even if the <branch> isn’t unique across all remotes. Set it to e.g.checkout.defaultRemote=originto always checkout remote -branches from there if <branch> is ambiguous but exists on the +branches from there if <branch> is ambiguous but exists on the origin remote. See alsocheckout.defaultRemotein git-config[1].OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of
gitcheckout<commit> when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior ofgitcheckout<commit> when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.- --orphan <new_branch>
@@ -358,9 +358,9 @@OPTIONS
- --patch
- -
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the “Interactive Mode” @@ -402,8 +402,8 @@OPTIONS
In the default overlay mode,
+working tree, but not in <tree-ish> are removed, to make them +match <tree-ish> exactly.gitcheckoutnever removes files from the index or the working tree. When specifying--no-overlay, files that appear in the index and -working tree, but not in <tree-ish> are removed, to make them -match <tree-ish> exactly.- --pathspec-from-file=<file>
- @@ -420,7 +420,7 @@
-OPTIONS
separated with NUL character and all other characters are taken literally (including newlines and quotes).- <branch>
+- <branch>
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -452,7 +452,7 @@
OPTIONS
leave out at most one ofAandB, in which case it defaults toHEAD.- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
@@ -461,7 +461,7 @@OPTIONS
- -
Do not interpret any more arguments as options.
- <pathspec>…
+- <pathspec>…
Limits the paths affected by the operation.
NAME
SYNOPSIS
-git checkout [-q] [-f] [-m] [<branch>] -git checkout [-q] [-f] [-m] --detach [<branch>] -git checkout [-q] [-f] [-m] [--detach] <commit> +git checkout [-q] [-f] [-m] [<branch>] +git checkout [-q] [-f] [-m] --detach [<branch>] +git checkout [-q] [-f] [-m] [--detach] <commit> git checkout [-q] [-f] [-m] [[-b|-B|--orphan] <new_branch>] [<start_point>] -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>… -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul] -git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]+git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>… +git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul] +git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]DESCRIPTION
@@ -70,25 +70,25 @@-
- git checkout [<branch>]
+- git checkout [<branch>]
- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing
+<branch>.HEADat the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name and
--no-guessis not specified, treat as equivalent to-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>-diff --git a/external/docs/content/docs/git-checkout/2.34.0.html b/external/docs/content/docs/git-checkout/2.34.0.html index 9496ea653d..99d377ec37 100644 --- a/external/docs/content/docs/git-checkout/2.34.0.html +++ b/external/docs/content/docs/git-checkout/2.34.0.html @@ -49,13 +49,13 @@You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with rather expensive side-effects to show only the tracking information, if exists, for the current branch.
@@ -135,8 +135,8 @@DESCRIPTION
--$ git branch -f <branch> [<start point>] -$ git checkout <branch>+$ git branch -f <branch> [<start point>] +$ git checkout <branch>- git checkout --detach [<branch>]
-- git checkout [--detach] <commit>
+- git checkout --detach [<branch>]
+- git checkout [--detach] <commit>
- -
-Prepare to work on top of <commit>, by detaching
HEADat it +Prepare to work on top of <commit>, by detaching
HEADat it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching--detachoption can be used to detachHEADat the tip of the branch (gitcheckout-<branch> would check out that branch without detachingHEAD).HEAD).-Omitting <branch> detaches
+HEADat the tip of the current branch.Omitting <branch> detaches
HEADat the tip of the current branch.- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
-- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
- -
Overwrite the contents of the files that match the pathspec. -When the <tree-ish> (most often a commit) is not given, +When the <tree-ish> (most often a commit) is not given, overwrite working tree with the contents in the index. -When the <tree-ish> is given, overwrite both the index and -the working tree with the contents at the <tree-ish>.
+When the <tree-ish> is given, overwrite both the index and +the working tree with the contents at the <tree-ish>.- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
+- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
This is similar to the previous mode, but lets you use the interactive interface to show the "diff" output and choose which @@ -281,21 +281,21 @@
OPTIONS
- --guess
- --no-guess
- -
If <branch> is not found but there does exist a tracking +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>@@ -317,8 +317,8 @@If the branch exists in multiple remotes and one of them is named by the
checkout.defaultRemoteconfiguration variable, we’ll use that -one for the purposes of disambiguation, even if the <branch> isn’t +one for the purposes of disambiguation, even if the <branch> isn’t unique across all remotes. Set it to e.g.checkout.defaultRemote=originto always checkout remote -branches from there if <branch> is ambiguous but exists on the +branches from there if <branch> is ambiguous but exists on the origin remote. See alsocheckout.defaultRemotein git-config[1].OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of
gitcheckout<commit> when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior ofgitcheckout<commit> when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.- --orphan <new_branch>
@@ -394,9 +394,9 @@OPTIONS
- --patch
- -
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the “Interactive Mode” @@ -438,8 +438,8 @@OPTIONS
In the default overlay mode,
+working tree, but not in <tree-ish> are removed, to make them +match <tree-ish> exactly.gitcheckoutnever removes files from the index or the working tree. When specifying--no-overlay, files that appear in the index and -working tree, but not in <tree-ish> are removed, to make them -match <tree-ish> exactly.- --pathspec-from-file=<file>
- @@ -456,7 +456,7 @@
-OPTIONS
separated with NUL character and all other characters are taken literally (including newlines and quotes).- <branch>
+- <branch>
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -488,7 +488,7 @@
OPTIONS
leave out at most one ofAandB, in which case it defaults toHEAD.- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
@@ -502,7 +502,7 @@OPTIONS
- -
Do not interpret any more arguments as options.
- <pathspec>…
+- <pathspec>…
Limits the paths affected by the operation.
NAME
SYNOPSIS
-git checkout [-q] [-f] [-m] [<branch>] -git checkout [-q] [-f] [-m] --detach [<branch>] -git checkout [-q] [-f] [-m] [--detach] <commit> +git checkout [-q] [-f] [-m] [<branch>] +git checkout [-q] [-f] [-m] --detach [<branch>] +git checkout [-q] [-f] [-m] [--detach] <commit> git checkout [-q] [-f] [-m] [[-b|-B|--orphan] <new_branch>] [<start_point>] -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>… -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul] -git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]+git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>… +git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul] +git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]DESCRIPTION
@@ -85,25 +85,25 @@-
- git checkout [<branch>]
+- git checkout [<branch>]
- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing
+<branch>.HEADat the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name and
--no-guessis not specified, treat as equivalent to-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>-diff --git a/external/docs/content/docs/git-checkout/2.35.0.html b/external/docs/content/docs/git-checkout/2.35.0.html index 5118aec2ff..362f48f642 100644 --- a/external/docs/content/docs/git-checkout/2.35.0.html +++ b/external/docs/content/docs/git-checkout/2.35.0.html @@ -64,13 +64,13 @@You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with rather expensive side-effects to show only the tracking information, if exists, for the current branch.
@@ -108,8 +108,8 @@DESCRIPTION
--$ git branch -f <branch> [<start point>] -$ git checkout <branch>+$ git branch -f <branch> [<start point>] +$ git checkout <branch>- git checkout --detach [<branch>]
-- git checkout [--detach] <commit>
+- git checkout --detach [<branch>]
+- git checkout [--detach] <commit>
- -
-Prepare to work on top of <commit>, by detaching
HEADat it +Prepare to work on top of <commit>, by detaching
HEADat it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching--detachoption can be used to detachHEADat the tip of the branch (gitcheckout-<branch> would check out that branch without detachingHEAD).HEAD).-Omitting <branch> detaches
+HEADat the tip of the current branch.Omitting <branch> detaches
HEADat the tip of the current branch.- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
-- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
- -
Overwrite the contents of the files that match the pathspec. -When the <tree-ish> (most often a commit) is not given, +When the <tree-ish> (most often a commit) is not given, overwrite working tree with the contents in the index. -When the <tree-ish> is given, overwrite both the index and -the working tree with the contents at the <tree-ish>.
+When the <tree-ish> is given, overwrite both the index and +the working tree with the contents at the <tree-ish>.- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
+- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
This is similar to the previous mode, but lets you use the interactive interface to show the "diff" output and choose which @@ -255,21 +255,21 @@
OPTIONS
- --guess
- --no-guess
- -
If <branch> is not found but there does exist a tracking +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>@@ -291,8 +291,8 @@If the branch exists in multiple remotes and one of them is named by the
checkout.defaultRemoteconfiguration variable, we’ll use that -one for the purposes of disambiguation, even if the <branch> isn’t +one for the purposes of disambiguation, even if the <branch> isn’t unique across all remotes. Set it to e.g.checkout.defaultRemote=originto always checkout remote -branches from there if <branch> is ambiguous but exists on the +branches from there if <branch> is ambiguous but exists on the origin remote. See alsocheckout.defaultRemotein git-config[1].OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of
gitcheckout<commit> when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior ofgitcheckout<commit> when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.- --orphan <new_branch>
@@ -368,9 +368,9 @@OPTIONS
- --patch
- -
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the “Interactive Mode” @@ -412,8 +412,8 @@OPTIONS
In the default overlay mode,
+working tree, but not in <tree-ish> are removed, to make them +match <tree-ish> exactly.gitcheckoutnever removes files from the index or the working tree. When specifying--no-overlay, files that appear in the index and -working tree, but not in <tree-ish> are removed, to make them -match <tree-ish> exactly.- --pathspec-from-file=<file>
- @@ -430,7 +430,7 @@
-OPTIONS
separated with NUL character and all other characters are taken literally (including newlines and quotes).- <branch>
+- <branch>
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -462,7 +462,7 @@
OPTIONS
leave out at most one ofAandB, in which case it defaults toHEAD.- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
@@ -476,7 +476,7 @@OPTIONS
- -
Do not interpret any more arguments as options.
- <pathspec>…
+- <pathspec>…
Limits the paths affected by the operation.
NAME
SYNOPSIS
-git checkout [-q] [-f] [-m] [<branch>] -git checkout [-q] [-f] [-m] --detach [<branch>] -git checkout [-q] [-f] [-m] [--detach] <commit> +git checkout [-q] [-f] [-m] [<branch>] +git checkout [-q] [-f] [-m] --detach [<branch>] +git checkout [-q] [-f] [-m] [--detach] <commit> git checkout [-q] [-f] [-m] [[-b|-B|--orphan] <new-branch>] [<start-point>] -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>… -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul] -git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]+git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>… +git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul] +git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]DESCRIPTION
@@ -72,25 +72,25 @@-
- git checkout [<branch>]
+- git checkout [<branch>]
- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing
+<branch>.HEADat the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name and
--no-guessis not specified, treat as equivalent to-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>-diff --git a/external/docs/content/docs/git-checkout/2.38.0.html b/external/docs/content/docs/git-checkout/2.38.0.html index 2da919406e..2b3cb9c77c 100644 --- a/external/docs/content/docs/git-checkout/2.38.0.html +++ b/external/docs/content/docs/git-checkout/2.38.0.html @@ -51,13 +51,13 @@You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with rather expensive side-effects to show only the tracking information, if exists, for the current branch.
@@ -123,8 +123,8 @@DESCRIPTION
--$ git branch -f <branch> [<start-point>] -$ git checkout <branch>+$ git branch -f <branch> [<start-point>] +$ git checkout <branch>- git checkout --detach [<branch>]
-- git checkout [--detach] <commit>
+- git checkout --detach [<branch>]
+- git checkout [--detach] <commit>
- -
-Prepare to work on top of <commit>, by detaching
HEADat it +Prepare to work on top of <commit>, by detaching
HEADat it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching--detachoption can be used to detachHEADat the tip of the branch (gitcheckout-<branch> would check out that branch without detachingHEAD).HEAD).-Omitting <branch> detaches
+HEADat the tip of the current branch.Omitting <branch> detaches
HEADat the tip of the current branch.- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
-- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
- -
Overwrite the contents of the files that match the pathspec. -When the <tree-ish> (most often a commit) is not given, +When the <tree-ish> (most often a commit) is not given, overwrite working tree with the contents in the index. -When the <tree-ish> is given, overwrite both the index and -the working tree with the contents at the <tree-ish>.
+When the <tree-ish> is given, overwrite both the index and +the working tree with the contents at the <tree-ish>.- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
+- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
This is similar to the previous mode, but lets you use the interactive interface to show the "diff" output and choose which @@ -270,21 +270,21 @@
OPTIONS
- --guess
- --no-guess
- -
If <branch> is not found but there does exist a tracking +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>@@ -306,8 +306,8 @@If the branch exists in multiple remotes and one of them is named by the
checkout.defaultRemoteconfiguration variable, we’ll use that -one for the purposes of disambiguation, even if the <branch> isn’t +one for the purposes of disambiguation, even if the <branch> isn’t unique across all remotes. Set it to e.g.checkout.defaultRemote=originto always checkout remote -branches from there if <branch> is ambiguous but exists on the +branches from there if <branch> is ambiguous but exists on the origin remote. See alsocheckout.defaultRemotein git-config[1].OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of
gitcheckout<commit> when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior ofgitcheckout<commit> when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.- --orphan <new-branch>
@@ -382,9 +382,9 @@OPTIONS
- --patch
- -
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the “Interactive Mode” @@ -426,8 +426,8 @@OPTIONS
In the default overlay mode,
+working tree, but not in <tree-ish> are removed, to make them +match <tree-ish> exactly.gitcheckoutnever removes files from the index or the working tree. When specifying--no-overlay, files that appear in the index and -working tree, but not in <tree-ish> are removed, to make them -match <tree-ish> exactly.- --pathspec-from-file=<file>
- @@ -444,7 +444,7 @@
-OPTIONS
separated with NUL character and all other characters are taken literally (including newlines and quotes).- <branch>
+- <branch>
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -476,7 +476,7 @@
OPTIONS
leave out at most one ofAandB, in which case it defaults toHEAD.- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
@@ -490,7 +490,7 @@OPTIONS
- -
Do not interpret any more arguments as options.
- <pathspec>…
+- <pathspec>…
Limits the paths affected by the operation.
NAME
SYNOPSIS
-git checkout [-q] [-f] [-m] [<branch>] -git checkout [-q] [-f] [-m] --detach [<branch>] -git checkout [-q] [-f] [-m] [--detach] <commit> +git checkout [-q] [-f] [-m] [<branch>] +git checkout [-q] [-f] [-m] --detach [<branch>] +git checkout [-q] [-f] [-m] [--detach] <commit> git checkout [-q] [-f] [-m] [[-b|-B|--orphan] <new-branch>] [<start-point>] -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>… -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul] -git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]+git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>… +git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul] +git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]DESCRIPTION
@@ -66,25 +66,25 @@-
- git checkout [<branch>]
+- git checkout [<branch>]
- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing
+<branch>.HEADat the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name and
--no-guessis not specified, treat as equivalent to-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>-diff --git a/external/docs/content/docs/git-checkout/2.39.3.html b/external/docs/content/docs/git-checkout/2.39.3.html index 349a72e346..cd7a39fa7d 100644 --- a/external/docs/content/docs/git-checkout/2.39.3.html +++ b/external/docs/content/docs/git-checkout/2.39.3.html @@ -45,13 +45,13 @@You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with rather expensive side-effects to show only the tracking information, if exists, for the current branch.
@@ -110,8 +110,8 @@DESCRIPTION
--$ git branch -f <branch> [<start-point>] -$ git checkout <branch>+$ git branch -f <branch> [<start-point>] +$ git checkout <branch>- git checkout --detach [<branch>]
-- git checkout [--detach] <commit>
+- git checkout --detach [<branch>]
+- git checkout [--detach] <commit>
- -
-Prepare to work on top of <commit>, by detaching
HEADat it +Prepare to work on top of <commit>, by detaching
HEADat it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching--detachoption can be used to detachHEADat the tip of the branch (gitcheckout-<branch> would check out that branch without detachingHEAD).HEAD).-Omitting <branch> detaches
+HEADat the tip of the current branch.Omitting <branch> detaches
HEADat the tip of the current branch.- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
-- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
- -
Overwrite the contents of the files that match the pathspec. -When the <tree-ish> (most often a commit) is not given, +When the <tree-ish> (most often a commit) is not given, overwrite working tree with the contents in the index. -When the <tree-ish> is given, overwrite both the index and -the working tree with the contents at the <tree-ish>.
+When the <tree-ish> is given, overwrite both the index and +the working tree with the contents at the <tree-ish>.- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
+- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
This is similar to the previous mode, but lets you use the interactive interface to show the "diff" output and choose which @@ -257,21 +257,21 @@
OPTIONS
- --guess
- --no-guess
- -
If <branch> is not found but there does exist a tracking +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>@@ -293,8 +293,8 @@If the branch exists in multiple remotes and one of them is named by the
checkout.defaultRemoteconfiguration variable, we’ll use that -one for the purposes of disambiguation, even if the <branch> isn’t +one for the purposes of disambiguation, even if the <branch> isn’t unique across all remotes. Set it to e.g.checkout.defaultRemote=originto always checkout remote -branches from there if <branch> is ambiguous but exists on the +branches from there if <branch> is ambiguous but exists on the origin remote. See alsocheckout.defaultRemotein git-config[1].OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of
gitcheckout<commit> when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior ofgitcheckout<commit> when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.- --orphan <new-branch>
@@ -369,9 +369,9 @@OPTIONS
- --patch
- -
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the “Interactive Mode” @@ -413,8 +413,8 @@OPTIONS
In the default overlay mode,
+working tree, but not in <tree-ish> are removed, to make them +match <tree-ish> exactly.gitcheckoutnever removes files from the index or the working tree. When specifying--no-overlay, files that appear in the index and -working tree, but not in <tree-ish> are removed, to make them -match <tree-ish> exactly.- --pathspec-from-file=<file>
- @@ -431,7 +431,7 @@
-OPTIONS
separated with NUL character and all other characters are taken literally (including newlines and quotes).- <branch>
+- <branch>
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -463,7 +463,7 @@
OPTIONS
leave out at most one ofAandB, in which case it defaults toHEAD.- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
@@ -477,7 +477,7 @@OPTIONS
- -
Do not interpret any more arguments as options.
- <pathspec>…
+- <pathspec>…
Limits the paths affected by the operation.
NAME
SYNOPSIS
-git checkout [-q] [-f] [-m] [<branch>] -git checkout [-q] [-f] [-m] --detach [<branch>] -git checkout [-q] [-f] [-m] [--detach] <commit> +git checkout [-q] [-f] [-m] [<branch>] +git checkout [-q] [-f] [-m] --detach [<branch>] +git checkout [-q] [-f] [-m] [--detach] <commit> git checkout [-q] [-f] [-m] [[-b|-B|--orphan] <new-branch>] [<start-point>] -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>… -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul] -git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]+git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>… +git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul] +git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]DESCRIPTION
@@ -57,25 +57,25 @@-
- git checkout [<branch>]
+- git checkout [<branch>]
- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing
+<branch>.HEADat the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name and
--no-guessis not specified, treat as equivalent to-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>-diff --git a/external/docs/content/docs/git-checkout/2.4.12.html b/external/docs/content/docs/git-checkout/2.4.12.html index 3477b924d5..097e11fee9 100644 --- a/external/docs/content/docs/git-checkout/2.4.12.html +++ b/external/docs/content/docs/git-checkout/2.4.12.html @@ -37,12 +37,12 @@You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with rather expensive side-effects to show only the tracking information, if exists, for the current branch.
@@ -104,8 +104,8 @@DESCRIPTION
--$ git branch -f <branch> [<start-point>] -$ git checkout <branch>+$ git branch -f <branch> [<start-point>] +$ git checkout <branch>- git checkout --detach [<branch>]
-- git checkout [--detach] <commit>
+- git checkout --detach [<branch>]
+- git checkout [--detach] <commit>
- -
-Prepare to work on top of <commit>, by detaching
HEADat it +Prepare to work on top of <commit>, by detaching
HEADat it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching--detachoption can be used to detachHEADat the tip of the branch (gitcheckout-<branch> would check out that branch without detachingHEAD).HEAD).-Omitting <branch> detaches
+HEADat the tip of the current branch.Omitting <branch> detaches
HEADat the tip of the current branch.- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
-- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
- -
Overwrite the contents of the files that match the pathspec. -When the <tree-ish> (most often a commit) is not given, +When the <tree-ish> (most often a commit) is not given, overwrite working tree with the contents in the index. -When the <tree-ish> is given, overwrite both the index and -the working tree with the contents at the <tree-ish>.
+When the <tree-ish> is given, overwrite both the index and +the working tree with the contents at the <tree-ish>.- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
+- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
This is similar to the previous mode, but lets you use the interactive interface to show the "diff" output and choose which @@ -253,21 +253,21 @@
OPTIONS
- --guess
- --no-guess
- -
If <branch> is not found but there does exist a tracking +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>@@ -289,8 +289,8 @@If the branch exists in multiple remotes and one of them is named by the
checkout.defaultRemoteconfiguration variable, we’ll use that -one for the purposes of disambiguation, even if the <branch> isn’t +one for the purposes of disambiguation, even if the <branch> isn’t unique across all remotes. Set it to e.g.checkout.defaultRemote=originto always checkout remote -branches from there if <branch> is ambiguous but exists on the +branches from there if <branch> is ambiguous but exists on the origin remote. See alsocheckout.defaultRemotein git-config[1].OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of
gitcheckout<commit> when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior ofgitcheckout<commit> when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.- --orphan <new-branch>
@@ -365,9 +365,9 @@OPTIONS
- --patch
- -
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the “Interactive Mode” @@ -409,8 +409,8 @@OPTIONS
In the default overlay mode,
+working tree, but not in <tree-ish> are removed, to make them +match <tree-ish> exactly.gitcheckoutnever removes files from the index or the working tree. When specifying--no-overlay, files that appear in the index and -working tree, but not in <tree-ish> are removed, to make them -match <tree-ish> exactly.- --pathspec-from-file=<file>
- @@ -427,7 +427,7 @@
-OPTIONS
separated with NUL character and all other characters are taken literally (including newlines and quotes).- <branch>
+- <branch>
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -459,7 +459,7 @@
OPTIONS
leave out at most one ofAandB, in which case it defaults toHEAD.- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
@@ -473,7 +473,7 @@OPTIONS
- -
Do not interpret any more arguments as options.
- <pathspec>…
+- <pathspec>…
Limits the paths affected by the operation.
NAME
SYNOPSIS
-git checkout [-q] [-f] [-m] [<branch>] -git checkout [-q] [-f] [-m] --detach [<branch>] -git checkout [-q] [-f] [-m] [--detach] <commit> +git checkout [-q] [-f] [-m] [<branch>] +git checkout [-q] [-f] [-m] --detach [<branch>] +git checkout [-q] [-f] [-m] [--detach] <commit> git checkout [-q] [-f] [-m] [[-b|-B|--orphan] <new_branch>] [<start_point>] -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <paths>… -git checkout [-p|--patch] [<tree-ish>] [--] [<paths>…]+git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <paths>… +git checkout [-p|--patch] [<tree-ish>] [--] [<paths>…]DESCRIPTION
-
- git checkout <branch>
+- git checkout <branch>
- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing HEAD at the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.
+<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>-You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with a rather expensive side-effects to show only the tracking information, if exists, for the current branch.
@@ -95,8 +95,8 @@DESCRIPTION
--$ git branch -f <branch> [<start point>] -$ git checkout <branch>+$ git branch -f <branch> [<start point>] +$ git checkout <branch>- git checkout --detach [<branch>]
-- git checkout [--detach] <commit>
+- git checkout --detach [<branch>]
+- git checkout [--detach] <commit>
- -
-Prepare to work on top of <commit>, by detaching HEAD at it +
Prepare to work on top of <commit>, by detaching HEAD at it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.
-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching HEAD).--detachoption can be used to detach HEAD at the tip of the branch (gitcheckout-<branch> would check out that branch without detaching HEAD).-Omitting <branch> detaches HEAD at the tip of the current branch.
+Omitting <branch> detaches HEAD at the tip of the current branch.
- git checkout [-p|--patch] [<tree-ish>] [--] <pathspec>…
+- git checkout [-p|--patch] [<tree-ish>] [--] <pathspec>…
When <paths> or
--patchare given, git checkout does not switch branches. It updates the named paths in the working tree -from the index file or from a named <tree-ish> (most often a +from the index file or from a named <tree-ish> (most often a commit). In this case, the-band--trackoptions are meaningless and giving either of them results in an error. The -<tree-ish> argument can be used to specify a specific tree-ish +<tree-ish> argument can be used to specify a specific tree-ish (i.e. commit, tag or tree) to update the index for the given paths before updating the working tree.git checkout with <paths> or
+with the contents from a named <tree-ish> (most often a commit-ish).--patchis used to restore modified or deleted paths to their original contents from the index or replace paths -with the contents from a named <tree-ish> (most often a commit-ish).@@ -68,25 +68,25 @@The index may contain unmerged entries because of a previous failed merge. @@ -222,8 +222,8 @@
OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of "git checkout <commit>" when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior of "git checkout <commit>" when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.
- --orphan <new_branch>
@@ -296,16 +296,16 @@OPTIONS
- --patch
- -
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the “Interactive Mode” section of git-add[1] to learn how to operate the--patchmode.- <branch>
+- <branch>
- -
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -332,7 +332,7 @@
OPTIONS
The name of a commit at which to start the new branch; see git-branch[1] for details. Defaults to HEAD.
- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
diff --git a/external/docs/content/docs/git-checkout/2.40.0.html b/external/docs/content/docs/git-checkout/2.40.0.html index 0694ed5934..a8d6a0f0d7 100644 --- a/external/docs/content/docs/git-checkout/2.40.0.html +++ b/external/docs/content/docs/git-checkout/2.40.0.html @@ -47,13 +47,13 @@NAME
SYNOPSIS
-git checkout [-q] [-f] [-m] [<branch>] -git checkout [-q] [-f] [-m] --detach [<branch>] -git checkout [-q] [-f] [-m] [--detach] <commit> +git checkout [-q] [-f] [-m] [<branch>] +git checkout [-q] [-f] [-m] --detach [<branch>] +git checkout [-q] [-f] [-m] [--detach] <commit> git checkout [-q] [-f] [-m] [[-b|-B|--orphan] <new-branch>] [<start-point>] -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>… -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul] -git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]+git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>… +git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul] +git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]DESCRIPTION
@@ -72,25 +72,25 @@-
- git checkout [<branch>]
+- git checkout [<branch>]
- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing
+<branch>.HEADat the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name and
--no-guessis not specified, treat as equivalent to-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>-diff --git a/external/docs/content/docs/git-checkout/2.41.0.html b/external/docs/content/docs/git-checkout/2.41.0.html index 3d334da03f..5604aa1aeb 100644 --- a/external/docs/content/docs/git-checkout/2.41.0.html +++ b/external/docs/content/docs/git-checkout/2.41.0.html @@ -51,13 +51,13 @@You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with rather expensive side-effects to show only the tracking information, if exists, for the current branch.
@@ -106,8 +106,8 @@DESCRIPTION
--$ git branch -f <branch> [<start-point>] -$ git checkout <branch>+$ git branch -f <branch> [<start-point>] +$ git checkout <branch>- git checkout --detach [<branch>]
-- git checkout [--detach] <commit>
+- git checkout --detach [<branch>]
+- git checkout [--detach] <commit>
- -
-Prepare to work on top of <commit>, by detaching
HEADat it +Prepare to work on top of <commit>, by detaching
HEADat it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching--detachoption can be used to detachHEADat the tip of the branch (gitcheckout-<branch> would check out that branch without detachingHEAD).HEAD).-Omitting <branch> detaches
+HEADat the tip of the current branch.Omitting <branch> detaches
HEADat the tip of the current branch.- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
-- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
- -
Overwrite the contents of the files that match the pathspec. -When the <tree-ish> (most often a commit) is not given, +When the <tree-ish> (most often a commit) is not given, overwrite working tree with the contents in the index. -When the <tree-ish> is given, overwrite both the index and -the working tree with the contents at the <tree-ish>.
+When the <tree-ish> is given, overwrite both the index and +the working tree with the contents at the <tree-ish>.- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
+- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
This is similar to the previous mode, but lets you use the interactive interface to show the "diff" output and choose which @@ -255,21 +255,21 @@
OPTIONS
- --guess
- --no-guess
- -
If <branch> is not found but there does exist a tracking +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>@@ -291,8 +291,8 @@If the branch exists in multiple remotes and one of them is named by the
checkout.defaultRemoteconfiguration variable, we’ll use that -one for the purposes of disambiguation, even if the <branch> isn’t +one for the purposes of disambiguation, even if the <branch> isn’t unique across all remotes. Set it to e.g.checkout.defaultRemote=originto always checkout remote -branches from there if <branch> is ambiguous but exists on the +branches from there if <branch> is ambiguous but exists on the origin remote. See alsocheckout.defaultRemotein git-config[1].OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of
gitcheckout<commit> when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior ofgitcheckout<commit> when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.- --orphan <new-branch>
@@ -367,9 +367,9 @@OPTIONS
- --patch
- -
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the “Interactive Mode” @@ -411,8 +411,8 @@OPTIONS
In the default overlay mode,
+working tree, but not in <tree-ish> are removed, to make them +match <tree-ish> exactly.gitcheckoutnever removes files from the index or the working tree. When specifying--no-overlay, files that appear in the index and -working tree, but not in <tree-ish> are removed, to make them -match <tree-ish> exactly.- --pathspec-from-file=<file>
- @@ -429,7 +429,7 @@
-OPTIONS
separated with NUL character and all other characters are taken literally (including newlines and quotes).- <branch>
+- <branch>
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -461,7 +461,7 @@
OPTIONS
leave out at most one ofAandB, in which case it defaults toHEAD.- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
@@ -475,7 +475,7 @@OPTIONS
- -
Do not interpret any more arguments as options.
- <pathspec>…
+- <pathspec>…
Limits the paths affected by the operation.
NAME
SYNOPSIS
-git checkout [-q] [-f] [-m] [<branch>] -git checkout [-q] [-f] [-m] --detach [<branch>] -git checkout [-q] [-f] [-m] [--detach] <commit> +git checkout [-q] [-f] [-m] [<branch>] +git checkout [-q] [-f] [-m] --detach [<branch>] +git checkout [-q] [-f] [-m] [--detach] <commit> git checkout [-q] [-f] [-m] [[-b|-B|--orphan] <new-branch>] [<start-point>] -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>… -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul] -git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]+git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>… +git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul] +git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]DESCRIPTION
@@ -66,25 +66,25 @@-
- git checkout [<branch>]
+- git checkout [<branch>]
- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing
+<branch>.HEADat the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name and
--no-guessis not specified, treat as equivalent to-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>-diff --git a/external/docs/content/docs/git-checkout/2.43.0.html b/external/docs/content/docs/git-checkout/2.43.0.html index 985684dd45..f248656769 100644 --- a/external/docs/content/docs/git-checkout/2.43.0.html +++ b/external/docs/content/docs/git-checkout/2.43.0.html @@ -43,15 +43,15 @@You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with rather expensive side-effects to show only the tracking information, if exists, for the current branch.
@@ -110,8 +110,8 @@DESCRIPTION
--$ git branch -f <branch> [<start-point>] -$ git checkout <branch>+$ git branch -f <branch> [<start-point>] +$ git checkout <branch>- git checkout --detach [<branch>]
-- git checkout [--detach] <commit>
+- git checkout --detach [<branch>]
+- git checkout [--detach] <commit>
- -
-Prepare to work on top of <commit>, by detaching
HEADat it +Prepare to work on top of <commit>, by detaching
HEADat it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching--detachoption can be used to detachHEADat the tip of the branch (gitcheckout-<branch> would check out that branch without detachingHEAD).HEAD).-Omitting <branch> detaches
+HEADat the tip of the current branch.Omitting <branch> detaches
HEADat the tip of the current branch.- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
-- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
- -
Overwrite the contents of the files that match the pathspec. -When the <tree-ish> (most often a commit) is not given, +When the <tree-ish> (most often a commit) is not given, overwrite working tree with the contents in the index. -When the <tree-ish> is given, overwrite both the index and -the working tree with the contents at the <tree-ish>.
+When the <tree-ish> is given, overwrite both the index and +the working tree with the contents at the <tree-ish>.- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
+- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
This is similar to the previous mode, but lets you use the interactive interface to show the "diff" output and choose which @@ -259,21 +259,21 @@
OPTIONS
- --guess
- --no-guess
- -
If <branch> is not found but there does exist a tracking +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>@@ -295,8 +295,8 @@If the branch exists in multiple remotes and one of them is named by the
checkout.defaultRemoteconfiguration variable, we’ll use that -one for the purposes of disambiguation, even if the <branch> isn’t +one for the purposes of disambiguation, even if the <branch> isn’t unique across all remotes. Set it to e.g.checkout.defaultRemote=originto always checkout remote -branches from there if <branch> is ambiguous but exists on the +branches from there if <branch> is ambiguous but exists on the origin remote. See alsocheckout.defaultRemotein git-config[1].OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of
gitcheckout<commit> when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior ofgitcheckout<commit> when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.- --orphan <new-branch>
@@ -371,9 +371,9 @@OPTIONS
- --patch
- -
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the “Interactive Mode” @@ -415,8 +415,8 @@OPTIONS
In the default overlay mode,
+working tree, but not in <tree-ish> are removed, to make them +match <tree-ish> exactly.gitcheckoutnever removes files from the index or the working tree. When specifying--no-overlay, files that appear in the index and -working tree, but not in <tree-ish> are removed, to make them -match <tree-ish> exactly.- --pathspec-from-file=<file>
- @@ -433,7 +433,7 @@
-OPTIONS
separated with NUL character and all other characters are taken literally (including newlines and quotes).- <branch>
+- <branch>
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -465,7 +465,7 @@
OPTIONS
leave out at most one ofAandB, in which case it defaults toHEAD.- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
@@ -479,7 +479,7 @@OPTIONS
- -
Do not interpret any more arguments as options.
- <pathspec>…
+- <pathspec>…
Limits the paths affected by the operation.
NAME
SYNOPSIS
-git checkout [-q] [-f] [-m] [<branch>] -git checkout [-q] [-f] [-m] --detach [<branch>] -git checkout [-q] [-f] [-m] [--detach] <commit> +git checkout [-q] [-f] [-m] [<branch>] +git checkout [-q] [-f] [-m] --detach [<branch>] +git checkout [-q] [-f] [-m] [--detach] <commit> git checkout [-q] [-f] [-m] [[-b|-B|--orphan] <new-branch>] [<start-point>] -git checkout [-f] <tree-ish> [--] <pathspec>… -git checkout [-f] <tree-ish> --pathspec-from-file=<file> [--pathspec-file-nul] -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [--] <pathspec>… +git checkout [-f] <tree-ish> [--] <pathspec>… +git checkout [-f] <tree-ish> --pathspec-from-file=<file> [--pathspec-file-nul] +git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [--] <pathspec>… git checkout [-f|--ours|--theirs|-m|--conflict=<style>] --pathspec-from-file=<file> [--pathspec-file-nul] -git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]+git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]DESCRIPTION
@@ -72,25 +72,25 @@-
- git checkout [<branch>]
+- git checkout [<branch>]
- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing
+<branch>.HEADat the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name and
--no-guessis not specified, treat as equivalent to-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>-diff --git a/external/docs/content/docs/git-checkout/2.43.1.html b/external/docs/content/docs/git-checkout/2.43.1.html index 5e1df2d458..6786cc1fdf 100644 --- a/external/docs/content/docs/git-checkout/2.43.1.html +++ b/external/docs/content/docs/git-checkout/2.43.1.html @@ -49,15 +49,15 @@You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with rather expensive side-effects to show only the tracking information, if it exists, for the current branch.
@@ -104,8 +104,8 @@DESCRIPTION
--$ git branch -f <branch> [<start-point>] -$ git checkout <branch>+$ git branch -f <branch> [<start-point>] +$ git checkout <branch>- git checkout --detach [<branch>]
-- git checkout [--detach] <commit>
+- git checkout --detach [<branch>]
+- git checkout [--detach] <commit>
- -
-Prepare to work on top of <commit>, by detaching
HEADat it +Prepare to work on top of <commit>, by detaching
HEADat it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching--detachoption can be used to detachHEADat the tip of the branch (gitcheckout-<branch> would check out that branch without detachingHEAD).HEAD).-Omitting <branch> detaches
+HEADat the tip of the current branch.Omitting <branch> detaches
HEADat the tip of the current branch.- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
-- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
- -
Overwrite the contents of the files that match the pathspec. -When the <tree-ish> (most often a commit) is not given, +When the <tree-ish> (most often a commit) is not given, overwrite working tree with the contents in the index. -When the <tree-ish> is given, overwrite both the index and -the working tree with the contents at the <tree-ish>.
+When the <tree-ish> is given, overwrite both the index and +the working tree with the contents at the <tree-ish>.- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
+- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
This is similar to the previous mode, but lets you use the interactive interface to show the "diff" output and choose which @@ -253,21 +253,21 @@
OPTIONS
- --guess
- --no-guess
- -
If <branch> is not found but there does exist a tracking +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>@@ -289,8 +289,8 @@If the branch exists in multiple remotes and one of them is named by the
checkout.defaultRemoteconfiguration variable, we’ll use that -one for the purposes of disambiguation, even if the <branch> isn’t +one for the purposes of disambiguation, even if the <branch> isn’t unique across all remotes. Set it to e.g.checkout.defaultRemote=originto always checkout remote -branches from there if <branch> is ambiguous but exists on the +branches from there if <branch> is ambiguous but exists on the origin remote. See alsocheckout.defaultRemotein git-config[1].OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of
gitcheckout<commit> when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior ofgitcheckout<commit> when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.- --orphan <new-branch>
@@ -366,9 +366,9 @@OPTIONS
- --patch
- -
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the “Interactive Mode” @@ -410,8 +410,8 @@OPTIONS
In the default overlay mode,
+working tree, but not in <tree-ish> are removed, to make them +match <tree-ish> exactly.gitcheckoutnever removes files from the index or the working tree. When specifying--no-overlay, files that appear in the index and -working tree, but not in <tree-ish> are removed, to make them -match <tree-ish> exactly.- --pathspec-from-file=<file>
- @@ -428,7 +428,7 @@
-OPTIONS
separated with NUL character and all other characters are taken literally (including newlines and quotes).- <branch>
+- <branch>
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -460,7 +460,7 @@
OPTIONS
leave out at most one ofAandB, in which case it defaults toHEAD.- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
@@ -474,7 +474,7 @@OPTIONS
- -
Do not interpret any more arguments as options.
- <pathspec>…
+- <pathspec>…
Limits the paths affected by the operation.
NAME
SYNOPSIS
-git checkout [-q] [-f] [-m] [<branch>] -git checkout [-q] [-f] [-m] --detach [<branch>] -git checkout [-q] [-f] [-m] [--detach] <commit> +git checkout [-q] [-f] [-m] [<branch>] +git checkout [-q] [-f] [-m] --detach [<branch>] +git checkout [-q] [-f] [-m] [--detach] <commit> git checkout [-q] [-f] [-m] [[-b|-B|--orphan] <new-branch>] [<start-point>] -git checkout [-f] <tree-ish> [--] <pathspec>… -git checkout [-f] <tree-ish> --pathspec-from-file=<file> [--pathspec-file-nul] -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [--] <pathspec>… +git checkout [-f] <tree-ish> [--] <pathspec>… +git checkout [-f] <tree-ish> --pathspec-from-file=<file> [--pathspec-file-nul] +git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [--] <pathspec>… git checkout [-f|--ours|--theirs|-m|--conflict=<style>] --pathspec-from-file=<file> [--pathspec-file-nul] -git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]+git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]DESCRIPTION
@@ -81,25 +81,25 @@-
- git checkout [<branch>]
+- git checkout [<branch>]
- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing
+<branch>.HEADat the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name and
--no-guessis not specified, treat as equivalent to-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>-diff --git a/external/docs/content/docs/git-checkout/2.44.0.html b/external/docs/content/docs/git-checkout/2.44.0.html index e39e520808..c72dcbc2a4 100644 --- a/external/docs/content/docs/git-checkout/2.44.0.html +++ b/external/docs/content/docs/git-checkout/2.44.0.html @@ -58,15 +58,15 @@You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with rather expensive side-effects to show only the tracking information, if it exists, for the current branch.
@@ -110,8 +110,8 @@DESCRIPTION
--$ git branch -f <branch> [<start-point>] -$ git checkout <branch>+$ git branch -f <branch> [<start-point>] +$ git checkout <branch>- git checkout --detach [<branch>]
-- git checkout [--detach] <commit>
+- git checkout --detach [<branch>]
+- git checkout [--detach] <commit>
- -
-Prepare to work on top of <commit>, by detaching
HEADat it +Prepare to work on top of <commit>, by detaching
HEADat it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching--detachoption can be used to detachHEADat the tip of the branch (gitcheckout-<branch> would check out that branch without detachingHEAD).HEAD).-Omitting <branch> detaches
+HEADat the tip of the current branch.Omitting <branch> detaches
HEADat the tip of the current branch.- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
-- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
- -
Overwrite the contents of the files that match the pathspec. -When the <tree-ish> (most often a commit) is not given, +When the <tree-ish> (most often a commit) is not given, overwrite working tree with the contents in the index. -When the <tree-ish> is given, overwrite both the index and -the working tree with the contents at the <tree-ish>.
+When the <tree-ish> is given, overwrite both the index and +the working tree with the contents at the <tree-ish>.- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
+- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
This is similar to the previous mode, but lets you use the interactive interface to show the "diff" output and choose which @@ -259,21 +259,21 @@
OPTIONS
- --guess
- --no-guess
- -
If <branch> is not found but there does exist a tracking +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>@@ -295,8 +295,8 @@If the branch exists in multiple remotes and one of them is named by the
checkout.defaultRemoteconfiguration variable, we’ll use that -one for the purposes of disambiguation, even if the <branch> isn’t +one for the purposes of disambiguation, even if the <branch> isn’t unique across all remotes. Set it to e.g.checkout.defaultRemote=originto always checkout remote -branches from there if <branch> is ambiguous but exists on the +branches from there if <branch> is ambiguous but exists on the origin remote. See alsocheckout.defaultRemotein git-config[1].OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of
gitcheckout<commit> when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior ofgitcheckout<commit> when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.- --orphan <new-branch>
@@ -372,9 +372,9 @@OPTIONS
- --patch
- -
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the “Interactive Mode” @@ -416,8 +416,8 @@OPTIONS
In the default overlay mode,
+working tree, but not in <tree-ish> are removed, to make them +match <tree-ish> exactly.gitcheckoutnever removes files from the index or the working tree. When specifying--no-overlay, files that appear in the index and -working tree, but not in <tree-ish> are removed, to make them -match <tree-ish> exactly.- --pathspec-from-file=<file>
- @@ -434,7 +434,7 @@
-OPTIONS
separated with NUL character and all other characters are taken literally (including newlines and quotes).- <branch>
+- <branch>
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -466,7 +466,7 @@
OPTIONS
leave out at most one ofAandB, in which case it defaults toHEAD.- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
@@ -480,7 +480,7 @@OPTIONS
- -
Do not interpret any more arguments as options.
- <pathspec>…
+- <pathspec>…
Limits the paths affected by the operation.
NAME
SYNOPSIS
-git checkout [-q] [-f] [-m] [<branch>] -git checkout [-q] [-f] [-m] --detach [<branch>] -git checkout [-q] [-f] [-m] [--detach] <commit> +git checkout [-q] [-f] [-m] [<branch>] +git checkout [-q] [-f] [-m] --detach [<branch>] +git checkout [-q] [-f] [-m] [--detach] <commit> git checkout [-q] [-f] [-m] [[-b|-B|--orphan] <new-branch>] [<start-point>] -git checkout [-f] <tree-ish> [--] <pathspec>… -git checkout [-f] <tree-ish> --pathspec-from-file=<file> [--pathspec-file-nul] -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [--] <pathspec>… +git checkout [-f] <tree-ish> [--] <pathspec>… +git checkout [-f] <tree-ish> --pathspec-from-file=<file> [--pathspec-file-nul] +git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [--] <pathspec>… git checkout [-f|--ours|--theirs|-m|--conflict=<style>] --pathspec-from-file=<file> [--pathspec-file-nul] -git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]+git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]DESCRIPTION
@@ -73,25 +73,25 @@-
- git checkout [<branch>]
+- git checkout [<branch>]
- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing
+<branch>.HEADat the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name and
--no-guessis not specified, treat as equivalent to-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>-diff --git a/external/docs/content/docs/git-checkout/2.47.1.html b/external/docs/content/docs/git-checkout/2.47.1.html index eb75bbd086..0527fe81d2 100644 --- a/external/docs/content/docs/git-checkout/2.47.1.html +++ b/external/docs/content/docs/git-checkout/2.47.1.html @@ -50,15 +50,15 @@You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with rather expensive side-effects to show only the tracking information, if it exists, for the current branch.
@@ -119,8 +119,8 @@DESCRIPTION
--$ git branch -f <branch> [<start-point>] -$ git checkout <branch>+$ git branch -f <branch> [<start-point>] +$ git checkout <branch>- git checkout --detach [<branch>]
-- git checkout [--detach] <commit>
+- git checkout --detach [<branch>]
+- git checkout [--detach] <commit>
- -
-Prepare to work on top of <commit>, by detaching
HEADat it +Prepare to work on top of <commit>, by detaching
HEADat it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching--detachoption can be used to detachHEADat the tip of the branch (gitcheckout-<branch> would check out that branch without detachingHEAD).HEAD).-Omitting <branch> detaches
+HEADat the tip of the current branch.Omitting <branch> detaches
HEADat the tip of the current branch.- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
-- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
- -
Overwrite the contents of the files that match the pathspec. -When the <tree-ish> (most often a commit) is not given, +When the <tree-ish> (most often a commit) is not given, overwrite working tree with the contents in the index. -When the <tree-ish> is given, overwrite both the index and -the working tree with the contents at the <tree-ish>.
+When the <tree-ish> is given, overwrite both the index and +the working tree with the contents at the <tree-ish>.- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
+- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
This is similar to the previous mode, but lets you use the interactive interface to show the "diff" output and choose which @@ -270,21 +270,21 @@
OPTIONS
- --guess
- --no-guess
- -
If <branch> is not found but there does exist a tracking +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>@@ -306,8 +306,8 @@If the branch exists in multiple remotes and one of them is named by the
checkout.defaultRemoteconfiguration variable, we’ll use that -one for the purposes of disambiguation, even if the <branch> isn’t +one for the purposes of disambiguation, even if the <branch> isn’t unique across all remotes. Set it to e.g.checkout.defaultRemote=originto always checkout remote -branches from there if <branch> is ambiguous but exists on the +branches from there if <branch> is ambiguous but exists on the origin remote. See alsocheckout.defaultRemotein git-config[1].OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of
gitcheckout<commit> when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior ofgitcheckout<commit> when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.- --orphan <new-branch>
@@ -383,9 +383,9 @@OPTIONS
- --patch
- -
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the “Interactive Mode” @@ -427,8 +427,8 @@OPTIONS
In the default overlay mode,
+working tree, but not in <tree-ish> are removed, to make them +match <tree-ish> exactly.gitcheckoutnever removes files from the index or the working tree. When specifying--no-overlay, files that appear in the index and -working tree, but not in <tree-ish> are removed, to make them -match <tree-ish> exactly.- --pathspec-from-file=<file>
- @@ -445,7 +445,7 @@
-OPTIONS
separated with NUL character and all other characters are taken literally (including newlines and quotes).- <branch>
+- <branch>
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -477,7 +477,7 @@
OPTIONS
leave out at most one ofAandB, in which case it defaults toHEAD.- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
@@ -491,7 +491,7 @@OPTIONS
- -
Do not interpret any more arguments as options.
- <pathspec>…
+- <pathspec>…
Limits the paths affected by the operation.
NAME
SYNOPSIS
-git checkout [-q] [-f] [-m] [<branch>] -git checkout [-q] [-f] [-m] --detach [<branch>] -git checkout [-q] [-f] [-m] [--detach] <commit> +git checkout [-q] [-f] [-m] [<branch>] +git checkout [-q] [-f] [-m] --detach [<branch>] +git checkout [-q] [-f] [-m] [--detach] <commit> git checkout [-q] [-f] [-m] [[-b|-B|--orphan] <new-branch>] [<start-point>] -git checkout [-f] <tree-ish> [--] <pathspec>… -git checkout [-f] <tree-ish> --pathspec-from-file=<file> [--pathspec-file-nul] -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [--] <pathspec>… +git checkout [-f] <tree-ish> [--] <pathspec>… +git checkout [-f] <tree-ish> --pathspec-from-file=<file> [--pathspec-file-nul] +git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [--] <pathspec>… git checkout [-f|--ours|--theirs|-m|--conflict=<style>] --pathspec-from-file=<file> [--pathspec-file-nul] -git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]+git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]DESCRIPTION
@@ -58,25 +58,25 @@-
- git checkout [<branch>]
+- git checkout [<branch>]
- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing
+<branch>.HEADat the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name and
--no-guessis not specified, treat as equivalent to-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>-diff --git a/external/docs/content/docs/git-checkout/2.5.6.html b/external/docs/content/docs/git-checkout/2.5.6.html index c79ddb1003..4596762446 100644 --- a/external/docs/content/docs/git-checkout/2.5.6.html +++ b/external/docs/content/docs/git-checkout/2.5.6.html @@ -38,12 +38,12 @@You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with rather expensive side-effects to show only the tracking information, if it exists, for the current branch.
@@ -111,8 +111,8 @@DESCRIPTION
--$ git branch -f <branch> [<start-point>] -$ git checkout <branch>+$ git branch -f <branch> [<start-point>] +$ git checkout <branch>- git checkout --detach [<branch>]
-- git checkout [--detach] <commit>
+- git checkout --detach [<branch>]
+- git checkout [--detach] <commit>
- -
-Prepare to work on top of <commit>, by detaching
HEADat it +Prepare to work on top of <commit>, by detaching
HEADat it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching--detachoption can be used to detachHEADat the tip of the branch (gitcheckout-<branch> would check out that branch without detachingHEAD).HEAD).-Omitting <branch> detaches
+HEADat the tip of the current branch.Omitting <branch> detaches
HEADat the tip of the current branch.- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
-- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>…
+- git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] --pathspec-from-file=<file> [--pathspec-file-nul]
- -
Overwrite the contents of the files that match the pathspec. -When the <tree-ish> (most often a commit) is not given, +When the <tree-ish> (most often a commit) is not given, overwrite working tree with the contents in the index. -When the <tree-ish> is given, overwrite both the index and -the working tree with the contents at the <tree-ish>.
+When the <tree-ish> is given, overwrite both the index and +the working tree with the contents at the <tree-ish>.- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
+- git checkout (-p|--patch) [<tree-ish>] [--] [<pathspec>…]
This is similar to the previous mode, but lets you use the interactive interface to show the "diff" output and choose which @@ -262,21 +262,21 @@
OPTIONS
- --guess
- --no-guess
- -
If <branch> is not found but there does exist a tracking +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>@@ -298,8 +298,8 @@If the branch exists in multiple remotes and one of them is named by the
checkout.defaultRemoteconfiguration variable, we’ll use that -one for the purposes of disambiguation, even if the <branch> isn’t +one for the purposes of disambiguation, even if the <branch> isn’t unique across all remotes. Set it to e.g.checkout.defaultRemote=originto always checkout remote -branches from there if <branch> is ambiguous but exists on the +branches from there if <branch> is ambiguous but exists on the origin remote. See alsocheckout.defaultRemotein git-config[1].OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of
gitcheckout<commit> when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior ofgitcheckout<commit> when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.- --orphan <new-branch>
@@ -375,9 +375,9 @@OPTIONS
- --patch
- -
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the “Interactive Mode” @@ -419,8 +419,8 @@OPTIONS
In the default overlay mode,
+working tree, but not in <tree-ish> are removed, to make them +match <tree-ish> exactly.gitcheckoutnever removes files from the index or the working tree. When specifying--no-overlay, files that appear in the index and -working tree, but not in <tree-ish> are removed, to make them -match <tree-ish> exactly.- --pathspec-from-file=<file>
- @@ -437,7 +437,7 @@
-OPTIONS
separated with NUL character and all other characters are taken literally (including newlines and quotes).- <branch>
+- <branch>
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -469,7 +469,7 @@
OPTIONS
leave out at most one ofAandB, in which case it defaults toHEAD.- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
@@ -483,7 +483,7 @@OPTIONS
- -
Do not interpret any more arguments as options.
- <pathspec>…
+- <pathspec>…
Limits the paths affected by the operation.
NAME
SYNOPSIS
-git checkout [-q] [-f] [-m] [<branch>] -git checkout [-q] [-f] [-m] --detach [<branch>] -git checkout [-q] [-f] [-m] [--detach] <commit> +git checkout [-q] [-f] [-m] [<branch>] +git checkout [-q] [-f] [-m] --detach [<branch>] +git checkout [-q] [-f] [-m] [--detach] <commit> git checkout [-q] [-f] [-m] [[-b|-B|--orphan] <new_branch>] [<start_point>] -git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <paths>… -git checkout [-p|--patch] [<tree-ish>] [--] [<paths>…]+git checkout [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <paths>… +git checkout [-p|--patch] [<tree-ish>] [--] [<paths>…]DESCRIPTION
-
- git checkout <branch>
+- git checkout <branch>
- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing HEAD at the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.
+<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>-You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with a rather expensive side-effects to show only the tracking information, if exists, for the current branch.
@@ -96,8 +96,8 @@DESCRIPTION
--$ git branch -f <branch> [<start point>] -$ git checkout <branch>+$ git branch -f <branch> [<start point>] +$ git checkout <branch>- git checkout --detach [<branch>]
-- git checkout [--detach] <commit>
+- git checkout --detach [<branch>]
+- git checkout [--detach] <commit>
- -
-Prepare to work on top of <commit>, by detaching HEAD at it +
Prepare to work on top of <commit>, by detaching HEAD at it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.
-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching HEAD).--detachoption can be used to detach HEAD at the tip of the branch (gitcheckout-<branch> would check out that branch without detaching HEAD).-Omitting <branch> detaches HEAD at the tip of the current branch.
+Omitting <branch> detaches HEAD at the tip of the current branch.
- git checkout [-p|--patch] [<tree-ish>] [--] <pathspec>…
+- git checkout [-p|--patch] [<tree-ish>] [--] <pathspec>…
When <paths> or
--patchare given, git checkout does not switch branches. It updates the named paths in the working tree -from the index file or from a named <tree-ish> (most often a +from the index file or from a named <tree-ish> (most often a commit). In this case, the-band--trackoptions are meaningless and giving either of them results in an error. The -<tree-ish> argument can be used to specify a specific tree-ish +<tree-ish> argument can be used to specify a specific tree-ish (i.e. commit, tag or tree) to update the index for the given paths before updating the working tree.git checkout with <paths> or
+with the contents from a named <tree-ish> (most often a commit-ish).--patchis used to restore modified or deleted paths to their original contents from the index or replace paths -with the contents from a named <tree-ish> (most often a commit-ish).The index may contain unmerged entries because of a previous failed merge. @@ -240,8 +240,8 @@
OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of "git checkout <commit>" when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior of "git checkout <commit>" when +<commit> is not a branch name. See the "DETACHED HEAD" section below for details.
- --orphan <new_branch>
@@ -314,9 +314,9 @@OPTIONS
- --patch
Interactively select hunks in the difference between the -<tree-ish> (or the index, if unspecified) and the working +<tree-ish> (or the index, if unspecified) and the working tree. The chosen hunks are then applied in reverse to the -working tree (and if a <tree-ish> was specified, the index).
+working tree (and if a <tree-ish> was specified, the index).@@ -67,25 +67,25 @@This means that you can use
gitcheckout-pto selectively discard edits from your current working tree. See the “Interactive Mode” @@ -330,7 +330,7 @@OPTIONS
out anyway. In other words, the ref can be held by more than one worktree. -- <branch>
+- <branch>
- -
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that @@ -357,7 +357,7 @@
OPTIONS
The name of a commit at which to start the new branch; see git-branch[1] for details. Defaults to HEAD.
- <tree-ish>
+- <tree-ish>
Tree to checkout from (when paths are given). If not specified, the index will be used.
diff --git a/external/docs/content/docs/git-checkout/2.50.0.html b/external/docs/content/docs/git-checkout/2.50.0.html index 2d7829ec6a..8f1f84d2a8 100644 --- a/external/docs/content/docs/git-checkout/2.50.0.html +++ b/external/docs/content/docs/git-checkout/2.50.0.html @@ -44,15 +44,15 @@NAME
SYNOPSIS
-gitcheckout[-q] [-f] [-m] [<branch>] -gitcheckout[-q] [-f] [-m]--detach[<branch>] -gitcheckout[-q] [-f] [-m] [--detach] <commit> ++gitcheckout[-q] [-f] [-m] [<branch>] +gitcheckout[-q] [-f] [-m]--detach[<branch>] +gitcheckout[-q] [-f] [-m] [--detach] <commit>gitcheckout[-q] [-f] [-m] [[-b|-B|--orphan] <new-branch>] [<start-point>] -gitcheckout[-f] <tree-ish> [--] <pathspec>… -gitcheckout[-f] <tree-ish>--pathspec-from-file=<file> [--pathspec-file-nul] -gitcheckout[-f|--ours|--theirs|-m|--conflict=<style>] [--] <pathspec>… +gitcheckout[-f] <tree-ish> [--] <pathspec>… +gitcheckout[-f] <tree-ish>--pathspec-from-file=<file> [--pathspec-file-nul] +gitcheckout[-f|--ours|--theirs|-m|--conflict=<style>] [--] <pathspec>…gitcheckout[-f|--ours|--theirs|-m|--conflict=<style>]--pathspec-from-file=<file> [--pathspec-file-nul] -gitcheckout(-p|--patch) [<tree-ish>] [--] [<pathspec>…]gitcheckout(-p|--patch) [<tree-ish>] [--] [<pathspec>…]DESCRIPTION
-
- +
gitcheckout[<branch>]gitcheckout[<branch>]- -
To prepare for working on <branch>, switch to it by updating +
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing
+<branch>.HEADat the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the -<branch>.-If <branch> is not found but there does exist a tracking branch in +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name and
--no-guessis not specified, treat as equivalent to-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>-You could omit <branch>, in which case the command degenerates to +
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with rather expensive side-effects to show only the tracking information, if it exists, for the current branch.
@@ -105,8 +105,8 @@DESCRIPTION
--$ git branch -f <branch> [<start-point>] -$ git checkout <branch>+$ git branch -f <branch> [<start-point>] +$ git checkout <branch>- -
gitcheckout--detach[<branch>]- +
gitcheckout[--detach] <commit>- +
gitcheckout--detach[<branch>]gitcheckout[--detach] <commit>- -
-Prepare to work on top of <commit>, by detaching
HEADat it +Prepare to work on top of <commit>, by detaching
HEADat it (see "DETACHED HEAD" section), and updating the index and the files in the working tree. Local modifications to the files in the working tree are kept, so that the resulting working tree will be the state recorded in the commit plus the local modifications.-When the <commit> argument is a branch name, the
--detachoption can +When the <commit> argument is a branch name, the
+<branch> would check out that branch without detaching--detachoption can be used to detachHEADat the tip of the branch (gitcheckout-<branch> would check out that branch without detachingHEAD).HEAD).-Omitting <branch> detaches
+HEADat the tip of the current branch.Omitting <branch> detaches
HEADat the tip of the current branch.- -
gitcheckout[-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>...- +
gitcheckout[-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>]--pathspec-from-file=<file> [--pathspec-file-nul]- +
gitcheckout[-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <pathspec>...gitcheckout[-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>]--pathspec-from-file=<file> [--pathspec-file-nul]- -
Overwrite the contents of the files that match the pathspec. -When the <tree-ish> (most often a commit) is not given, +When the <tree-ish> (most often a commit) is not given, overwrite working tree with the contents in the index. -When the <tree-ish> is given, overwrite both the index and -the working tree with the contents at the <tree-ish>.
+When the <tree-ish> is given, overwrite both the index and +the working tree with the contents at the <tree-ish>.- +
gitcheckout(-p|--patch) [<tree-ish>] [--] [<pathspec>...]gitcheckout(-p|--patch) [<tree-ish>] [--] [<pathspec>...]This is similar to the previous mode, but lets you use the interactive interface to show the "diff" output and choose which @@ -256,21 +256,21 @@
OPTIONS
--guess--no-guess- -
If <branch> is not found but there does exist a tracking +
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
-$ git checkout -b <branch> --track <remote>/<branch>+$ git checkout -b <branch> --track <remote>/<branch>@@ -292,8 +292,8 @@If the branch exists in multiple remotes and one of them is named by the
checkout.defaultRemoteconfiguration variable, we’ll use that -one for the purposes of disambiguation, even if the <branch> isn’t +one for the purposes of disambiguation, even if the <branch> isn’t unique across all remotes. Set it to e.g.checkout.defaultRemote=originto always checkout remote -branches from there if <branch> is ambiguous but exists on the +branches from there if <branch> is ambiguous but exists on the origin remote. See alsocheckout.defaultRemotein git-config[1].OPTIONS
Rather than checking out a branch to work on it, check out a commit for inspection and discardable experiments. -This is the default behavior of
gitcheckout<commit> when -<commit> is not a branch name. See the "DETACHED HEAD" section +This is the default behavior ofgitcheckout