libv8 4.5.95.5 → 5.0.71.48.0beta2

data/vendor/depot_tools/man/man1/git-rebase-update.1

@@ -2,12 +2,12 @@
 .\"     Title: git-rebase-update
 .\"    Author: [FIXME: author] [see http://docbook.sf.net/el/author]
 .\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
-.\"      Date: 04/10/2014
+.\"      Date: 09/10/2015
 .\"    Manual: Chromium depot_tools Manual
-.\"    Source: depot_tools 68b1017
+.\"    Source: depot_tools 805792e
 .\"  Language: English
 .\"
-.TH "GIT\-REBASE\-UPDATE" "1" "04/10/2014" "depot_tools 68b1017" "Chromium depot_tools Manual"
+.TH "GIT\-REBASE\-UPDATE" "1" "09/10/2015" "depot_tools 805792e" "Chromium depot_tools Manual"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -32,7 +32,7 @@ git-rebase-update \- Updates all branches to have the latest changes from their
 .SH "SYNOPSIS"
 .sp
 .nf
-\fIgit rebase\-update\fR [\-v | \-\-verbose] [\-n | \-\-no_fetch]
+\fIgit rebase\-update\fR [\-v | \-\-verbose] [\-n | \-\-no\-fetch] [\-k | \-\-keep\-going]
 .fi
 .sp
 .SH "DESCRIPTION"
@@ -58,7 +58,7 @@ Fetching
 All branches are examined to find their upstream references\&. The correct set of git remotes is determined, and fetched accordingly\&. Note that if any branches have a tag as their upstream, we are forced to pull all remotes\&.
 .sp
 Pass
-\-\-no_fetch
+\-\-no\-fetch
 to skip this phase\&.
 .RE
 .PP
@@ -87,6 +87,8 @@ will exit\&. You can deal with this like any other conflicted rebase\&. When you
 git rebase\-update
 again to pick up where you left off\&.
 .RE
+.sp
+If you\(cqd like to rebase all rebaseable branches in one pass and manually process the unrebaseable ones later, use \-k or \-\-keep\-going\&. Cleanup will not happen until all branches apply cleanly\&.
 .PP
 Cleanup
 .RS 4
@@ -111,7 +113,7 @@ depot\-tools\&.upstream, see
 .RE
 .SH "OPTIONS"
 .PP
-\-n, \-\-no_fetch
+\-n, \-\-no\-fetch
 .RS 4
 Skip the
 git fetch

data/vendor/depot_tools/man/man7/depot_tools.7

@@ -1,13 +1,13 @@
 '\" t
 .\"     Title: depot_tools
 .\"    Author: [FIXME: author] [see http://docbook.sf.net/el/author]
-.\" Generator: DocBook XSL Stylesheets v1.76.1 <http://docbook.sf.net/>
-.\"      Date: 09/09/2014
+.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\"      Date: 01/28/2016
 .\"    Manual: Chromium depot_tools Manual
-.\"    Source: depot_tools 40ce153
+.\"    Source: depot_tools 7143379
 .\"  Language: English
 .\"
-.TH "DEPOT_TOOLS" "7" "09/09/2014" "depot_tools 40ce153" "Chromium depot_tools Manual"
+.TH "DEPOT_TOOLS" "7" "01/28/2016" "depot_tools 7143379" "Chromium depot_tools Manual"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -62,6 +62,11 @@ Extract meta\-information expressed as footers in a commit message\&.
 Freeze all changes on a branch (indexed and unindexed)\&.
 .RE
 .PP
+\fBgit-hyper-blame\fR(1)
+.RS 4
+Like git blame, but with the ability to ignore or bypass certain commits\&.
+.RE
+.PP
 \fBgit-map-branches\fR(1)
 .RS 4
 Helper script to display all local git branches with \(oqupstream\(cq hierarchy in colorized terminal format\&.

data/vendor/depot_tools/man/src/_git-hyper-blame_desc.helper.txt

@@ -0,0 +1 @@
+Like git blame, but with the ability to ignore or bypass certain commits.

data/vendor/depot_tools/man/src/common_demo_functions.sh

@@ -50,6 +50,11 @@ comment() {
   echo "###COMMENT### $@"
 }
 
+# run a command and print its output without printing the command itself
+output() {
+  "$@"
+}
+
 # run a silent command
 silent() {
   if [[ $DEBUG ]]

data/vendor/depot_tools/man/src/depot_tools_tutorial.txt

@@ -88,7 +88,7 @@ ifdef::backend-xhtml11[]
 WINDOWS
 ^^^^^^^
 Download the 'depot_tools'
-link:https://src.chromium.org/svn/trunk/tools/depot_tools.zip[bundle] and
+link:https://storage.googleapis.com/chrome-infra/depot_tools.zip[bundle] and
 extract it somewhere.
 
 [WARNING]

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

@@ -3,25 +3,20 @@
 
 drover_c "This change needs to go to branch 9999"
 
-echo "# Make sure we have the most up-to-date branch sources."
-run git fetch
-echo
 echo "# Here's a commit (from some.committer) that we want to 'drover'."
 run git log -n 1 --pretty=fuller
 echo
-echo "# Checkout the branch we want to 'drover' to."
-run git checkout -b drover_9999 branch-heads/9999
-echo
 echo "# Now do the 'drover'."
-echo "# IMPORTANT!!! Do Not leave off the '-x' flag"
-run git cherry-pick -x $(git show-ref -s pick_commit)
+pcommand git drover --branch 9999 \
+  --cherry-pick $(git show-ref -s pick_commit)
+
+echo "Going to cherry-pick"
+echo '"""'
+output git log -n 1
+echo '"""'
+echo "to 9999. Continue (y/n)? y"
 echo
-echo "# That took the code authored by some.committer and committed it to"
-echo "# the branch by the person who drovered it (i.e. you)."
-run git log -n 1 --pretty=fuller
+echo "# A cl is uploaded to rietveld, where it can be reviewed before landing."
 echo
-echo "# Looks good. Ship it!"
-pcommand git cl upload
-echo "# Wait for LGTM or TBR it."
-run git cl land
-echo "# Or skip the LGTM/TBR and just 'git cl land --bypass-hooks'"
+echo "About to land on 9999. Continue (y/n)? y"
+echo "# The cherry-pick cl is landed on the branch 9999."

data/vendor/depot_tools/man/src/git-drover.demo.3.sh

@@ -0,0 +1,27 @@
+#!/usr/bin/env bash
+. git-drover.demo.common.sh
+
+drover_c "This change needs to go to branch 9999"
+
+echo "# Make sure we have the most up-to-date branch sources."
+run git fetch
+echo
+echo "# Here's a commit (from some.committer) that we want to 'drover'."
+run git log -n 1 --pretty=fuller
+echo
+echo "# Checkout the branch we want to 'drover' to."
+run git checkout -b drover_9999 branch-heads/9999
+echo
+echo "# Now do the 'drover'."
+echo "# IMPORTANT!!! Do Not leave off the '-x' flag"
+run git cherry-pick -x $(git show-ref -s pick_commit)
+echo
+echo "# That took the code authored by some.committer and committed it to"
+echo "# the branch by the person who drovered it (i.e. you)."
+run git log -n 1 --pretty=fuller
+echo
+echo "# Looks good. Ship it!"
+pcommand git cl upload
+echo "# Wait for LGTM or TBR it."
+run git cl land
+echo "# Or skip the LGTM/TBR and just 'git cl land --bypass-hooks'"

data/vendor/depot_tools/man/src/git-drover.demo.4.sh

@@ -0,0 +1,39 @@
+#!/usr/bin/env bash
+. git-drover.demo.common.sh
+
+drover_c "This change needs to go to branch 9999"
+
+echo "# Here's a commit (from some.committer) that we want to 'drover'."
+run git log -n 1 --pretty=fuller
+echo
+echo "# Now do the 'drover'."
+pcommand git drover --branch 9999 \
+  --cherry-pick $(git show-ref -s pick_commit)
+
+echo "Going to cherry-pick"
+echo '"""'
+output git log -n 1
+echo '"""'
+echo "to 9999. Continue (y/n)? y"
+echo
+echo "Error: Patch failed to apply."
+echo
+echo "A workdir for this cherry-pick has been created in"
+echo "  /tmp/drover_9999"
+echo
+echo "To continue, resolve the conflicts there and run"
+echo "  git drover --continue /tmp/drover_9999"
+echo
+echo "To abort this cherry-pick run"
+echo "  git drover --abort /tmp/drover_9999"
+echo
+pcommand pushd /tmp/drover_9999
+echo "# Manually resolve conflicts."
+pcommand git add path/to/file_with_conflicts
+pcommand popd
+pcommand git drover --continue /tmp/drover_9999
+echo
+echo "# A cl is uploaded to rietveld, where it can be reviewed before landing."
+echo
+echo "About to land on 9999. Continue (y/n)? y"
+echo "# The cherry-pick cl is landed on the branch 9999."

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

@@ -9,13 +9,51 @@ include::_git-drover_desc.helper.txt[]
 SYNOPSIS
 --------
 [verse]
-'git drover'
+'git drover' --branch <branch>
+           (--cherry-pick <change> | --continue [path_to_workdir] |
+            --abort [path_to_workdir])
+           [--parent_checkout <path-to-existing-checkout>]
+           [--verbose] [--dry-run]
 
 DESCRIPTION
 -----------
 
-`git drover` is NOT IMPLEMENTED yet. See the EXAMPLE section for the equivalent
-sequence of commands to run.
+`git drover` applies a commit to a release branch. It creates a new workdir from
+an existing checkout to avoid downloading a new checkout without affecting the
+existing checkout.
+
+`git drover` does not support reverts. See the EXAMPLE section for the
+equivalent sequence of commands to run.
+
+OPTIONS
+-------
+--branch <branch>::
+  The branch to cherry-pick the commit to.
+
+--cherry-pick <commit>::
+  The commit to cherry-pick.
+
+--continue [path_to_workdir]::
+  Continue a cherry-pick that required manual resolution. The path to the drover
+  workdir is optional. If unspecified, the current directory is used.
+
+--abort [path_to_workdir]::
+  Abort a cherry-pick that required manual resolution and clean up its workdir.
+  The path to the drover workdir is optional. If unspecified, the current
+  directory is used.
+
+--parent_checkout::
+  The path to the chromium checkout to use as the source for a creating
+  git-new-workdir workdir to use for cherry-picking. If unspecified, the current
+  directory is used.
+
+-v::
+--verbose::
+  Enable verbose logging.
+
+--dry-run::
+  Skip landing the cherry-pick. Just ensure that the commit can be cherry-picked
+  into the branch.
 
 EXAMPLE
 -------
@@ -35,10 +73,18 @@ Merge Example
 ^^^^^^^^^^^^^
 demo:1[]
 
+Merge with Conflicts Example
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+demo:4[]
+
 Revert Example
 ^^^^^^^^^^^^^^
 demo:2[]
 
+Manual Merge Example
+^^^^^^^^^^^^^^^^^^^^
+demo:3[]
+
 SEE ALSO
 --------
 linkgit:git-cherry-pick[1], linkgit:git-revert[1]

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-rebase-update.txt

@@ -9,7 +9,7 @@ include::_git-rebase-update_desc.helper.txt[]
 SYNOPSIS
 --------
 [verse]
-'git rebase-update' [-v | --verbose] [-n | --no-fetch]
+'git rebase-update' [-v | --verbose] [-n | --no-fetch] [-k | --keep-going]
 
 DESCRIPTION
 -----------
@@ -49,6 +49,10 @@ left in mid-rebase and `git rebase-update` will exit. You can deal with this
 like any other conflicted rebase. When you're done, just `git rebase-update`
 again to pick up where you left off.
 
+If you'd like to rebase all rebaseable branches in one pass and manually process
+the unrebaseable ones later, use -k or --keep-going. Cleanup will not happen
+until all branches apply cleanly.
+
 Cleanup::
   Once all the branches have been rebased, any empty branches (i.e. branches
   with no commits on them) are removed. If a branch is removed in this fashion,