libv8 8.4.255.0

data/vendor/depot_tools/man/src/git-footers.demo.1.sh

@@ -0,0 +1,17 @@
+#!/usr/bin/env bash
+. demo_repo.sh
+
+add deleted_file
+add unstaged_deleted_file
+add modified_file
+c 'I committed this and am proud of it.
+
+Cr-Commit-Position: refs/heads/master@{#292272}
+Tech-Debt-Introduced: 17 microMSOffices
+Tech-Debt-Introduced: -4 microMSOffices'
+
+run git footers HEAD
+run git footers --key Tech-Debt-Introduced HEAD
+run git footers --position HEAD
+run git footers --position-num HEAD
+run git footers --position-ref HEAD

data/vendor/depot_tools/man/src/git-footers.txt

@@ -0,0 +1,71 @@
+git-footers(1)
+==============
+
+NAME
+----
+git-footers -
+include::_git-footers_desc.helper.txt[]
+
+SYNOPSIS
+--------
+[verse]
+'git footers' [--key FOOTER] REF
+'git footers' [--position | --position-ref | --position-num] REF
+
+DESCRIPTION
+-----------
+
+`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:
+
+    This is a fancy commit message.
+
+    Cr-Commit-Position: refs/heads/master@{#292272}
+    Tech-Debt-Introduced: 17 nanoMSOffices
+
+`git footers` knows how to extract this information.
+
+Footers are order-independent and can appear more than once. Thus they are
+treated as a multimap.
+
+OPTIONS
+-------
+
+If no options are given, all footers are printed, with their names
+case-normalized.
+
+--key FOOTER::
+  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.
+
+--position::
+  Extract the Chrome commit position from the footers.  This first attempts
+  to get the value of the `Cr-Commit-Position` footer.  If that doesn't exist
+  then it tries a heuristic based on `Git-Svn-Id`.  Output is in one of the
+  following forms:
+
+    refs/heads/master@{#292272}
+    refs/branch-heads/branchname
+
+--position-num::
+  Extracts and prints the Chrome commit position number only (292272 in the
+  example above).  Exits with an error if one cannot be found.
+
+--position-ref::
+  Extracts and prints the Chrome commit position ref name only 
+  (`ref/heads/master` or `refs/branch-heads/branchname` in the example above).
+
+
+EXAMPLE
+-------
+demo:1[]
+
+SEE ALSO
+--------
+linkgit:git-number[1]
+
+include::_footer.txt[]
+
+// vim: ft=asciidoc:

data/vendor/depot_tools/man/src/git-freeze.demo.1.sh

@@ -0,0 +1,23 @@
+#!/usr/bin/env bash
+. demo_repo.sh
+
+add deleted_file
+add unstaged_deleted_file
+add modified_file
+c "demo changes"
+
+add added_file_with_unstaged_changes
+echo bob >> added_file_with_unstaged_changes
+
+add added_file
+echo bob >> modified_file
+silent git rm deleted_file
+rm unstaged_deleted_file
+touch unadded_file
+
+run git status --short
+run git freeze
+run git status --short
+run git log -n 2 --stat
+run git thaw
+run git status --short

data/vendor/depot_tools/man/src/git-freeze.txt

@@ -0,0 +1,54 @@
+git-freeze(1)
+=============
+
+NAME
+----
+git-freeze -
+include::_git-freeze_desc.helper.txt[]
+
+SYNOPSIS
+--------
+[verse]
+'git freeze'
+
+DESCRIPTION
+-----------
+
+`git freeze` works a lot like `git stash`, in that it stores the current changes
+in your working copy and index 'somewhere'. Unlike `git stash`, `git freeze`
+stores those changes on your current branch. This effectively allows you to
+'pause' development of a branch, work on something else, and then come back to
+exactly the same working state later (by running `git thaw`).
+
+`git freeze` will make up to 2 commits on your branch. A commit with the message
+`FREEZE.indexed` will contain all changes which you’ve added to your index (like
+with 'git add', 'git mv', 'git rm', 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.).
+
+By default `git freeze` will only freeze up to 100MB of untracked files. See
+'CONFIGURATION VARIABLES' for more details.
+
+
+EXAMPLE
+-------
+demo:1[]
+
+
+CONFIGURATION VARIABLES
+-----------------------
+
+depot-tools.freeze-size-limit
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+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. *100* by default.
+
+
+SEE ALSO
+--------
+linkgit:git-thaw[1]
+
+include::_footer.txt[]
+
+// vim: ft=asciidoc:

data/vendor/depot_tools/man/src/git-hyper-blame.demo.1.sh

@@ -0,0 +1,3 @@
+#!/usr/bin/env bash
+. git-hyper-blame.demo.common.sh
+run git blame ipsum.txt

data/vendor/depot_tools/man/src/git-hyper-blame.demo.2.sh

@@ -0,0 +1,4 @@
+#!/usr/bin/env bash
+. git-hyper-blame.demo.common.sh
+IGNORE=$(git rev-parse HEAD^)
+run git hyper-blame -i ${IGNORE:0:8} ipsum.txt

data/vendor/depot_tools/man/src/git-hyper-blame.demo.common.sh

@@ -0,0 +1,57 @@
+#!/usr/bin/env bash
+. demo_repo.sh
+
+# Construct a plausible file history.
+set_user "lorem"
+V1="Lorem ipsum dolor sit amet, consectetur*
+adipiscing elit, sed do eiusmod tempor
+incididunt ut labore et dolore magna*
+aliqua. Ut enim ad minim veniam, quis
+nostrud exercitation ullamco laboris**
+nisi ut aliquip ex ea commodo consequat.*"
+add "ipsum.txt" "$V1"
+c "Added Lorem Ipsum"
+tick 95408
+
+set_user "ipsum"
+V2="Lorem ipsum dolor sit amet, consectetur*
+adipiscing elit, sed do eiusmod tempor
+incididunt ut labore et dolore magna
+aliqua. Ut enim ad minim veniam, quis
+nostrud exercitation ullamco laboris**
+nisi ut aliquip ex ea commodo consequat.*"
+add "ipsum.txt" "$V2"
+c "Change 1"
+tick 4493194
+
+set_user "dolor"
+V3="Lorem ipsum dolor sit amet, consectetur*
+adipiscing elit, sed do eiusmod tempor
+incididunt ut labore et dolore magna
+aliqua. Ut enim ad minim veniam, quis
+nostrud exercitation ullamco laboris*
+nisi ut aliquip ex ea commodo consequat."
+add "ipsum.txt" "$V3"
+c "Change 2"
+tick 2817200
+
+set_user "auto-uppercaser"
+V4="LOREM IPSUM DOLOR SIT AMET, CONSECTETUR*
+ADIPISCING ELIT, SED DO EIUSMOD TEMPOR
+INCIDIDUNT UT LABORE ET DOLORE MAGNA
+ALIQUA. UT ENIM AD MINIM VENIAM, QUIS
+NOSTRUD EXERCITATION ULLAMCO LABORIS*
+NISI UT ALIQUIP EX EA COMMODO CONSEQUAT."
+add "ipsum.txt" "$V4"
+c "Automatic upper-casing of all text."
+tick 3273029
+
+set_user "lorem"
+V4="LOREM IPSUM DOLOR SIT AMET, CONSECTETUR
+ADIPISCING ELIT, SED DO EIUSMOD TEMPOR
+INCIDIDUNT UT LABORE ET DOLORE MAGNA
+ALIQUA. UT ENIM AD MINIM VENIAM, QUIS
+NOSTRUD EXERCITATION ULLAMCO LABORIS
+NISI UT ALIQUIP EX EA COMMODO CONSEQUAT."
+add "ipsum.txt" "$V4"
+c "Change 3."

data/vendor/depot_tools/man/src/git-hyper-blame.txt

@@ -0,0 +1,85 @@
+git-hyper-blame(1)
+==================
+
+NAME
+----
+git-hyper-blame -
+include::_git-hyper-blame_desc.helper.txt[]
+
+SYNOPSIS
+--------
+[verse]
+'git hyper-blame' [-i <rev> [-i <rev> ...]] [--ignore-file=<file>]
+                [--no-default-ignores] [<rev>] [--] <file>
+
+DESCRIPTION
+-----------
+
+`git hyper-blame` is like `git blame` but it can ignore or "look through" a
+given set of commits, to find the real culprit.
+
+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.
+
+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.
+
+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.
+
+OPTIONS
+-------
+
+-i <rev>::
+  A revision to ignore. Can be specified as many times as needed.
+
+--ignore-file=<file>::
+  A file containing a list of revisions to ignore. Can have comments beginning
+  with `#`.
+
+--no-default-ignores::
+  Do not ignore commits from the `.git-blame-ignore-revs` file.
+
+EXAMPLE
+-------
+
+Let's run `git blame` on a file:
+
+demo:1[]
+
+Notice that almost the entire file has been blamed on a formatting change? You
+aren't 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:
+
+demo:2[]
+
+`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.
+
+CAVEATS
+-------
+
+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.
+
+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.
+
+SEE ALSO
+--------
+linkgit:git-blame[1]
+
+include::_footer.txt[]
+
+// vim: ft=asciidoc:

data/vendor/depot_tools/man/src/git-map-branches.demo.1.sh

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+. demo_repo.sh
+
+silent git branch no_upstream HEAD~
+
+run git map-branches
+run git map-branches -v
+

data/vendor/depot_tools/man/src/git-map-branches.txt

@@ -0,0 +1,64 @@
+git-map-branches(1)
+===================
+
+NAME
+----
+git-map-branches -
+include::_git-map-branches_desc.helper.txt[]
+
+SYNOPSIS
+--------
+[verse]
+'git map-branches'
+
+DESCRIPTION
+-----------
+
+Git map-branches displays all local branches such that:
+
+* Current branch is [aqua]#cyan#.
+** The branch which will be modified with git-commit is denoted with an asterisk
+   (`*`) after the name.
+* Local branches are [green]#green#.
+* Remote branches are [red]#red# (usually, the root of all other branches).
+* 'branch-heads' branches are [blue]#blue#.
+* `{NO UPSTREAM}` is a special placeholder in [fuchsia]#magenta#.
+** 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>.
+
+NOTE: If multiple branches are on the same commit, they will all be cyan.
+
+OPTIONS
+-------
+
+--no-color::
+  Turn off colors.
+
+-v::
+  Be more verbose. Pass once to show tracking info, twice for hash and review
+  URL, thrice for review status.
+
+EXAMPLE
+-------
+
+Given the hypothetical demo repo in linkgit:git-map[1]\'s EXAMPLE section, and
+assuming that the `frozen_changes` branch was currently checked out, running
+'git map-branches' would result in an output like:
+
+demo:1[]
+
+include::_aliases.txt[]
+
+----
+[alias]
+  git bmap = map-branches
+----
+
+SEE ALSO
+--------
+linkgit:git-map[1]
+
+include::_footer.txt[]
+
+// vim: ft=asciidoc:

data/vendor/depot_tools/man/src/git-map.demo.1.sh

@@ -0,0 +1,3 @@
+#!/usr/bin/env bash
+. demo_repo.sh
+run git map

data/vendor/depot_tools/man/src/git-map.txt

@@ -0,0 +1,67 @@
+git-map(1)
+==========
+
+NAME
+----
+git-map -
+include::_git-map_desc.helper.txt[]
+
+SYNOPSIS
+--------
+[verse]
+'git map' [<extra_args>...]
+
+DESCRIPTION
+-----------
+
+Git map formats the output of `git log --graph` from all refs such that:
+
+* Current branch is [aqua]#cyan#.
+* Local branches are [green]#green#.
+* Remote branches are [red]#red#.
+* Tags are [fuchsia]#magenta#.
+* Merge Base markers are [black-background white]#white#.
+* The currently checked out commit is highlighted with a [yellow blue-background]#blue background#.
+
+The output is automatically piped through the `less` pager command, even on
+windows.
+
+OPTIONS
+-------
+<extra_args>...::
+  Extra parameters to pass to the internal linkgit:git-log[1] invocation. This
+  can be used to restrict what refs 'git map' operates on, etc.
++
+If you run git map with a series of fixed arguments frequently, you can use
+the depot-tools.map-extra configuration variable to pre-set arguments (See
+`CONFIGURATION VARIABLES`)
+
+
+CONFIGURATION VARIABLES
+-----------------------
+
+depot-tools.map-extra
+~~~~~~~~~~~~~~~~~~~~~
+
+Each value of the 'depot-tools.map-extra' config variable is applied as an
+additional argument to `git log` during the execution of git map. If you wish to
+configure this, use git `config --add depot-tools.map-extra <value>` to do so.
+
+EXAMPLE
+-------
+
+Running 'git map' would result in an output something like:
+demo:1[]
+
+As you can see, the structure of the commit history is visible, particularly
+what the parents of each commit are.  In order to see the 'upstream'
+relationships of the branches (i.e. which branch is tracking which other
+branch), use the linkgit:git-map-branches[1] command.
+
+SEE ALSO
+--------
+linkgit:git-map-branches[1]
+
+include::_footer.txt[]
+
+// vim: ft=asciidoc: