5 Commits

Author	SHA1	Message	Date
Camillo Bruni	28ae216877	[tools] Show first V8 branch in mergeinfo.py ... Change-Id: I169b4d91463cb59aa2a91e79eda2d7e877f88d72 Reviewed-on: https://chromium-review.googlesource.com/456319 Commit-Queue: Camillo Bruni <cbruni@chromium.org> Reviewed-by: Michael Hablich <hablich@chromium.org> Cr-Commit-Position: refs/heads/master@{#44338}	2017-04-03 13:28:44 +00:00
clemensh	9d3b8fce50	[mergeinfo.py] Use remotes/origin/master instead of master ... I don't have a local master branch, so those commands failed for me. R=hablich@chromium.org NOTRY=true Review-Url: https://codereview.chromium.org/2733923002 Cr-Commit-Position: refs/heads/master@{#43752}	2017-03-13 16:22:26 +00:00
hablich	e267936c42	[Release] Remove usage of roll ref ... The roll ref is no longer used because we simply roll the lkgr ref. LOG=N NOTRY=true R=machenbach@chromium.org Review URL: https://codereview.chromium.org/1391153002 Cr-Commit-Position: refs/heads/master@{#31140}	2015-10-07 10:27:23 +00:00
hablich	8499fa2505	[Release] Distinguish between merges and follow-up CLs ... With this change mergeinfo.py gets more useful. There is a distinction between merges and follow-up CLs/ports/reverts. Also the information is show if the commit is already rolled/an lkgr/deployed to Canary channel. Additionally some formatting errors were resolved and the already existing git wrapper used. LOG=N R=machenbach@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/1341303002 Cr-Commit-Position: refs/heads/master@{#31043}	2015-10-01 11:29:16 +00:00
hablich	ef7e6fb165	usage: Tool to check where a git commit was merged and reverted. ... [-h] [-g GIT_DIR] hash positional arguments: hash Hash of the commit to be searched. optional arguments: -h, --help show this help message and exit -g GIT_DIR, --git-dir GIT_DIR The path to your git working directory. BUG= Review URL: https://codereview.chromium.org/1033043002 Cr-Commit-Position: refs/heads/master@{#27563}	2015-04-01 09:42:15 +00:00