libv8 8.4.255.0

data/vendor/depot_tools/man/man1/git-footers.1

@@ -0,0 +1,144 @@
+'\" t
+.\"     Title: git-footers
+.\"    Author: [FIXME: author] [see http://docbook.sf.net/el/author]
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
+.\"      Date: 05/03/2019
+.\"    Manual: Chromium depot_tools Manual
+.\"    Source: depot_tools e58cce6c
+.\"  Language: English
+.\"
+.TH "GIT\-FOOTERS" "1" "05/03/2019" "depot_tools e58cce6c" "Chromium depot_tools Manual"
+.\" -----------------------------------------------------------------
+.\" * Define some portability stuff
+.\" -----------------------------------------------------------------
+.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+.\" http://bugs.debian.org/507673
+.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
+.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+.ie \n(.g .ds Aq \(aq
+.el       .ds Aq '
+.\" -----------------------------------------------------------------
+.\" * set default formatting
+.\" -----------------------------------------------------------------
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.\" -----------------------------------------------------------------
+.\" * MAIN CONTENT STARTS HERE *
+.\" -----------------------------------------------------------------
+.SH "NAME"
+git-footers \- Extract meta\-information expressed as footers in a commit message\&.
+.SH "SYNOPSIS"
+.sp
+.nf
+\fIgit footers\fR [\-\-key FOOTER] REF
+\fIgit footers\fR [\-\-position | \-\-position\-ref | \-\-position\-num] REF
+.fi
+.sp
+.SH "DESCRIPTION"
+.sp
+git footers extracts information included in commit messages as "footers", which are roughly like HTTP headers except they are at the end\&. For example, a commit might look like:
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+This is a fancy commit message\&.
+.fi
+.if n \{\
+.RE
+.\}
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+Cr\-Commit\-Position: refs/heads/master@{#292272}
+Tech\-Debt\-Introduced: 17 nanoMSOffices
+.fi
+.if n \{\
+.RE
+.\}
+.sp
+git footers knows how to extract this information\&.
+.sp
+Footers are order\-independent and can appear more than once\&. Thus they are treated as a multimap\&.
+.SH "OPTIONS"
+.sp
+If no options are given, all footers are printed, with their names case\-normalized\&.
+.PP
+\-\-key FOOTER
+.RS 4
+Extract all the headers associated with the given key, and print one per line\&. If there are no footers with this key, produces no output and exits successfully\&.
+.RE
+.PP
+\-\-position
+.RS 4
+Extract the Chrome commit position from the footers\&. This first attempts to get the value of the
+Cr\-Commit\-Position
+footer\&. If that doesn\(cqt exist then it tries a heuristic based on
+Git\-Svn\-Id\&. Output is in one of the following forms:
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+refs/heads/master@{#292272}
+refs/branch\-heads/branchname
+.fi
+.if n \{\
+.RE
+.\}
+.RE
+.PP
+\-\-position\-num
+.RS 4
+Extracts and prints the Chrome commit position number only (292272 in the example above)\&. Exits with an error if one cannot be found\&.
+.RE
+.PP
+\-\-position\-ref
+.RS 4
+Extracts and prints the Chrome commit position ref name only (ref/heads/master
+or
+refs/branch\-heads/branchname
+in the example above)\&.
+.RE
+.SH "EXAMPLE"
+.sp
+
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+\fB$ git footers HEAD\fR
+Tech\-Debt\-Introduced: \-4 microMSOffices
+Tech\-Debt\-Introduced: 17 microMSOffices
+Cr\-Commit\-Position: refs/heads/master@{#292272}
+\fB$ git footers \-\-key Tech\-Debt\-Introduced HEAD\fR
+\-4 microMSOffices
+17 microMSOffices
+\fB$ git footers \-\-position HEAD\fR
+refs/heads/master@{#292272}
+\fB$ git footers \-\-position\-num HEAD\fR
+292272
+\fB$ git footers \-\-position\-ref HEAD\fR
+refs/heads/master
+.fi
+.if n \{\
+.RE
+.\}
+.sp
+.SH "SEE ALSO"
+.sp
+\fBgit-number\fR(1)
+.SH "CHROMIUM DEPOT_TOOLS"
+.sp
+Part of the chromium \fBdepot_tools\fR(7) suite\&. These tools are meant to assist with the development of chromium and related projects\&. Download the tools from \m[blue]\fBhere\fR\m[]\&\s-2\u[1]\d\s+2\&.
+.SH "NOTES"
+.IP " 1." 4
+here
+.RS 4
+\%https://chromium.googlesource.com/chromium/tools/depot_tools.git
+.RE

data/vendor/depot_tools/man/man1/git-freeze.1

@@ -0,0 +1,113 @@
+'\" t
+.\"     Title: git-freeze
+.\"    Author: [FIXME: author] [see http://docbook.sf.net/el/author]
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
+.\"      Date: 05/03/2019
+.\"    Manual: Chromium depot_tools Manual
+.\"    Source: depot_tools e58cce6c
+.\"  Language: English
+.\"
+.TH "GIT\-FREEZE" "1" "05/03/2019" "depot_tools e58cce6c" "Chromium depot_tools Manual"
+.\" -----------------------------------------------------------------
+.\" * Define some portability stuff
+.\" -----------------------------------------------------------------
+.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+.\" http://bugs.debian.org/507673
+.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
+.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+.ie \n(.g .ds Aq \(aq
+.el       .ds Aq '
+.\" -----------------------------------------------------------------
+.\" * set default formatting
+.\" -----------------------------------------------------------------
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.\" -----------------------------------------------------------------
+.\" * MAIN CONTENT STARTS HERE *
+.\" -----------------------------------------------------------------
+.SH "NAME"
+git-freeze \- Freeze all changes on a branch (indexed and unindexed)\&.
+.SH "SYNOPSIS"
+.sp
+.nf
+\fIgit freeze\fR
+.fi
+.sp
+.SH "DESCRIPTION"
+.sp
+git freeze works a lot like git stash, in that it stores the current changes in your working copy and index \fIsomewhere\fR\&. Unlike git stash, git freeze stores those changes on your current branch\&. This effectively allows you to \fIpause\fR development of a branch, work on something else, and then come back to exactly the same working state later (by running git thaw)\&.
+.sp
+git freeze will make up to 2 commits on your branch\&. A commit with the message FREEZE\&.indexed will contain all changes which you\(cqve added to your index (like with \fIgit add\fR, \fIgit mv\fR, \fIgit rm\fR, etc\&.)\&. A commit with the message FREEZE\&.unindexed will contain all changes which were not in your index at the time you ran git freeze (freshly modified files, new files, etc\&.)\&.
+.sp
+By default git freeze will only freeze up to 100MB of untracked files\&. See \fICONFIGURATION VARIABLES\fR for more details\&.
+.SH "EXAMPLE"
+.sp
+
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+\fB$ git status \-\-short\fR
+A  added_file
+AM added_file_with_unstaged_changes
+D  deleted_file
+ M modified_file
+ D unstaged_deleted_file
+?? unadded_file
+\fB$ git freeze\fR
+\fB$ git status \-\-short\fR
+\fB$ git log \-n 2 \-\-stat\fR
+commit d2b155e804b71d99ce51280d2fb9a56917351680
+Author: local <local@chromium\&.org>
+Date:   Thu Apr 10 08:54:56 2014 +0000
+
+    FREEZE\&.unindexed
+
+ added_file_with_unstaged_changes | 1 +
+ modified_file                    | 1 +
+ unadded_file                     | 0
+ unstaged_deleted_file            | 1 \-
+ 4 files changed, 2 insertions(+), 1 deletion(\-)
+
+commit bc45c733e95a18f2b2f641e31c7792441cb7da21
+Author: local <local@chromium\&.org>
+Date:   Thu Apr 10 08:54:56 2014 +0000
+
+    FREEZE\&.indexed
+
+ added_file                       | 1 +
+ added_file_with_unstaged_changes | 1 +
+ deleted_file                     | 1 \-
+ 3 files changed, 2 insertions(+), 1 deletion(\-)
+\fB$ git thaw\fR
+\fB$ git status \-\-short\fR
+A  added_file
+AM added_file_with_unstaged_changes
+D  deleted_file
+ M modified_file
+ D unstaged_deleted_file
+?? unadded_file
+.fi
+.if n \{\
+.RE
+.\}
+.sp
+.SH "CONFIGURATION VARIABLES"
+.SS "depot\-tools\&.freeze\-size\-limit"
+.sp
+This sets the size limit as an integer number of megabytes of untracked files that git\-freeze will be willing to put in suspended animation\&. A 0 or negative limit disables the size\-limit check entirely\&. \fB100\fR by default\&.
+.SH "SEE ALSO"
+.sp
+\fBgit-thaw\fR(1)
+.SH "CHROMIUM DEPOT_TOOLS"
+.sp
+Part of the chromium \fBdepot_tools\fR(7) suite\&. These tools are meant to assist with the development of chromium and related projects\&. Download the tools from \m[blue]\fBhere\fR\m[]\&\s-2\u[1]\d\s+2\&.
+.SH "NOTES"
+.IP " 1." 4
+here
+.RS 4
+\%https://chromium.googlesource.com/chromium/tools/depot_tools.git
+.RE

data/vendor/depot_tools/man/man1/git-hyper-blame.1

@@ -0,0 +1,128 @@
+'\" t
+.\"     Title: git-hyper-blame
+.\"    Author: [FIXME: author] [see http://docbook.sf.net/el/author]
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
+.\"      Date: 05/03/2019
+.\"    Manual: Chromium depot_tools Manual
+.\"    Source: depot_tools e58cce6c
+.\"  Language: English
+.\"
+.TH "GIT\-HYPER\-BLAME" "1" "05/03/2019" "depot_tools e58cce6c" "Chromium depot_tools Manual"
+.\" -----------------------------------------------------------------
+.\" * Define some portability stuff
+.\" -----------------------------------------------------------------
+.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+.\" http://bugs.debian.org/507673
+.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
+.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+.ie \n(.g .ds Aq \(aq
+.el       .ds Aq '
+.\" -----------------------------------------------------------------
+.\" * set default formatting
+.\" -----------------------------------------------------------------
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.\" -----------------------------------------------------------------
+.\" * MAIN CONTENT STARTS HERE *
+.\" -----------------------------------------------------------------
+.SH "NAME"
+git-hyper-blame \- Like git blame, but with the ability to ignore or bypass certain commits\&.
+.SH "SYNOPSIS"
+.sp
+.nf
+\fIgit hyper\-blame\fR [\-i <rev> [\-i <rev> \&...]] [\-\-ignore\-file=<file>]
+                [\-\-no\-default\-ignores] [<rev>] [\-\-] <file>
+.fi
+.sp
+.SH "DESCRIPTION"
+.sp
+git hyper\-blame is like git blame but it can ignore or "look through" a given set of commits, to find the real culprit\&.
+.sp
+This is useful if you have a commit that makes sweeping changes that are unlikely to be what you are looking for in a blame, such as mass reformatting or renaming\&. By adding these commits to the hyper\-blame ignore list, git hyper\-blame will look past these commits to find the previous commit that touched a given line\&.
+.sp
+Follows the normal blame syntax: annotates <file> with the revision that last modified each line\&. Optional <rev> specifies the revision of <file> to start from\&.
+.sp
+Automatically looks for a file called \&.git\-blame\-ignore\-revs in the repository root directory\&. This file has the same syntax as the \-\-ignore\-file argument, and any commits mentioned in this file are added to the ignore list\&.
+.SH "OPTIONS"
+.PP
+\-i <rev>
+.RS 4
+A revision to ignore\&. Can be specified as many times as needed\&.
+.RE
+.PP
+\-\-ignore\-file=<file>
+.RS 4
+A file containing a list of revisions to ignore\&. Can have comments beginning with
+#\&.
+.RE
+.PP
+\-\-no\-default\-ignores
+.RS 4
+Do not ignore commits from the
+\&.git\-blame\-ignore\-revs
+file\&.
+.RE
+.SH "EXAMPLE"
+.sp
+Let\(cqs run git blame on a file:
+.sp
+
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+\fB$ git blame ipsum\&.txt\fR
+c6eb3bfa (lorem           2014\-08\-11 23:15:57 +0000 1) LOREM IPSUM DOLOR SIT AMET, CONSECTETUR
+3ddda43c (auto\-uppercaser 2014\-07\-05 02:05:18 +0000 2) ADIPISCING ELIT, SED DO EIUSMOD TEMPOR
+3ddda43c (auto\-uppercaser 2014\-07\-05 02:05:18 +0000 3) INCIDIDUNT UT LABORE ET DOLORE MAGNA
+3ddda43c (auto\-uppercaser 2014\-07\-05 02:05:18 +0000 4) ALIQUA\&. UT ENIM AD MINIM VENIAM, QUIS
+c6eb3bfa (lorem           2014\-08\-11 23:15:57 +0000 5) NOSTRUD EXERCITATION ULLAMCO LABORIS
+3ddda43c (auto\-uppercaser 2014\-07\-05 02:05:18 +0000 6) NISI UT ALIQUIP EX EA COMMODO CONSEQUAT\&.
+.fi
+.if n \{\
+.RE
+.\}
+.sp
+.sp
+Notice that almost the entire file has been blamed on a formatting change? You aren\(cqt interested in the uppercasing of the file\&. You want to know who wrote/modified those lines in the first place\&. Just tell hyper\-blame to ignore that commit:
+.sp
+
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+\fB$ git hyper\-blame \-i 3ddda43c ipsum\&.txt\fR
+c6eb3bfa (lorem 2014\-08\-11 23:15:57 +0000  1) LOREM IPSUM DOLOR SIT AMET, CONSECTETUR
+134200d1 (lorem 2014\-04\-10 08:54:46 +0000 2*) ADIPISCING ELIT, SED DO EIUSMOD TEMPOR
+a34a1d0d (ipsum 2014\-04\-11 11:25:04 +0000 3*) INCIDIDUNT UT LABORE ET DOLORE MAGNA
+134200d1 (lorem 2014\-04\-10 08:54:46 +0000 4*) ALIQUA\&. UT ENIM AD MINIM VENIAM, QUIS
+c6eb3bfa (lorem 2014\-08\-11 23:15:57 +0000  5) NOSTRUD EXERCITATION ULLAMCO LABORIS
+0f0d17bd (dolor 2014\-06\-02 11:31:48 +0000 6*) NISI UT ALIQUIP EX EA COMMODO CONSEQUAT\&.
+.fi
+.if n \{\
+.RE
+.\}
+.sp
+.sp
+hyper\-blame places a * next to any line where it has skipped over an ignored commit, so you know that the line in question has been changed (by an ignored commit) since the given person wrote it\&.
+.SH "CAVEATS"
+.sp
+When a line skips over an ignored commit, a guess is made as to which commit previously modified that line, but it is not always clear where the line came from\&. If the ignored commit makes lots of changes in close proximity, in particular adding/removing/reordering lines, then the wrong authors may be blamed for nearby edits\&.
+.sp
+For this reason, hyper\-blame works best when the ignored commits are be limited to minor changes such as formatting and renaming, not refactoring or other more invasive changes\&.
+.SH "SEE ALSO"
+.sp
+\fBgit-blame\fR(1)
+.SH "CHROMIUM DEPOT_TOOLS"
+.sp
+Part of the chromium \fBdepot_tools\fR(7) suite\&. These tools are meant to assist with the development of chromium and related projects\&. Download the tools from \m[blue]\fBhere\fR\m[]\&\s-2\u[1]\d\s+2\&.
+.SH "NOTES"
+.IP " 1." 4
+here
+.RS 4
+\%https://chromium.googlesource.com/chromium/tools/depot_tools.git
+.RE

data/vendor/depot_tools/man/man1/git-map-branches.1

@@ -0,0 +1,210 @@
+'\" t
+.\"     Title: git-map-branches
+.\"    Author: [FIXME: author] [see http://docbook.sf.net/el/author]
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
+.\"      Date: 05/03/2019
+.\"    Manual: Chromium depot_tools Manual
+.\"    Source: depot_tools e58cce6c
+.\"  Language: English
+.\"
+.TH "GIT\-MAP\-BRANCHES" "1" "05/03/2019" "depot_tools e58cce6c" "Chromium depot_tools Manual"
+.\" -----------------------------------------------------------------
+.\" * Define some portability stuff
+.\" -----------------------------------------------------------------
+.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+.\" http://bugs.debian.org/507673
+.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
+.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+.ie \n(.g .ds Aq \(aq
+.el       .ds Aq '
+.\" -----------------------------------------------------------------
+.\" * set default formatting
+.\" -----------------------------------------------------------------
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.\" -----------------------------------------------------------------
+.\" * MAIN CONTENT STARTS HERE *
+.\" -----------------------------------------------------------------
+.SH "NAME"
+git-map-branches \- Helper script to display all local git branches with \(oqupstream\(cq hierarchy in colorized terminal format\&.
+.SH "SYNOPSIS"
+.sp
+.nf
+\fIgit map\-branches\fR
+.fi
+.sp
+.SH "DESCRIPTION"
+.sp
+Git map\-branches displays all local branches such that:
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+Current branch is
+cyan\&.
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+The branch which will be modified with git\-commit is denoted with an asterisk (*) after the name\&.
+.RE
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+Local branches are
+green\&.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+Remote branches are
+red
+(usually, the root of all other branches)\&.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\fIbranch\-heads\fR
+branches are
+blue\&.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+{NO UPSTREAM}
+is a special placeholder in
+magenta\&.
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+Branches which have this as their parent are usually misconfigured, and should be assigned a parent by checking out the branch and running git branch \-\-set\-upstream\-to=<correct parent branch>\&.
+.RE
+.RE
+.if n \{\
+.sp
+.\}
+.RS 4
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+.ps +1
+\fBNote\fR
+.ps -1
+.br
+.sp
+If multiple branches are on the same commit, they will all be cyan\&.
+.sp .5v
+.RE
+.SH "OPTIONS"
+.PP
+\-\-no\-color
+.RS 4
+Turn off colors\&.
+.RE
+.PP
+\-v
+.RS 4
+Be more verbose\&. Pass once to show tracking info, twice for hash and review URL, thrice for review status\&.
+.RE
+.SH "EXAMPLE"
+.sp
+Given the hypothetical demo repo in \fBgit-map\fR(1)\*(Aqs EXAMPLE section, and assuming that the frozen_changes branch was currently checked out, running \fIgit map\-branches\fR would result in an output like:
+.sp
+
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+\fB$ git map\-branches\fR
+{NO_UPSTREAM}
+  no_upstream
+origin/master
+  cool_feature
+    subfeature
+  fixit
+\fB    frozen_branch *
+$ git map\-branches \-v\fR
+{NO_UPSTREAM}
+  no_upstream
+origin/master
+  cool_feature         [ ahead 4            ]
+    subfeature         [ ahead 2 | behind 1 ]
+  fixit                [ ahead 2            ]
+\fB    frozen_branch *    [ ahead 3            ]\fR
+.fi
+.if n \{\
+.RE
+.\}
+.sp
+.SH "SUGGESTED ALIASES"
+.sp
+Some common short\-hand aliases\&. Feel free to add these to your \fI~/\&.gitconfig\fR file\&.
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+[alias]
+  git bmap = map\-branches
+.fi
+.if n \{\
+.RE
+.\}
+.sp
+.SH "SEE ALSO"
+.sp
+\fBgit-map\fR(1)
+.SH "CHROMIUM DEPOT_TOOLS"
+.sp
+Part of the chromium \fBdepot_tools\fR(7) suite\&. These tools are meant to assist with the development of chromium and related projects\&. Download the tools from \m[blue]\fBhere\fR\m[]\&\s-2\u[1]\d\s+2\&.
+.SH "NOTES"
+.IP " 1." 4
+here
+.RS 4
+\%https://chromium.googlesource.com/chromium/tools/depot_tools.git
+.RE