git-map - Issue 184113002: Add git-map and git-short-map to depot_tools.

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: git-map

Issue 184113002: Add git-map and git-short-map to depot_tools. (Closed) Base URL: https://chromium.googlesource.com/chromium/tools/depot_tools.git@new_branch

Patch Set: rebase and add better way to run python git extensions Created 6 years, 9 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch

OLD	NEW
1 #!/bin/bash	1 #!/bin/bash
	agable 2014/02/28 19:54:58 Yes, it is really nice that all of these tiny litt Yes, it is really nice that all of these tiny little bash scripts are just the same piece of boilerplate due to python_git_runner. But they should point at their python scripts directly in a comment so it is easy for someone figuring out what they do to find it. iannucci 2014/03/06 00:18:39 Really? What if I rename `python_git_runner.sh` -> Show quoted text On 2014/02/28 19:54:58, agable wrote: > Yes, it is really nice that all of these tiny little bash scripts are just the > same piece of boilerplate due to python_git_runner. But they should point at > their python scripts directly in a comment so it is easy for someone figuring > out what they do to find it. Really? What if I rename `python_git_runner.sh` -> `run_python_git_wrapper_named_the_same_as_argv_0.sh` It's obvious that this script does only one thing, which is forward to python_git_runner. The docs in that script should make it obvious what's going on, right? I'll introduce this launcher refactor in a parent CL.
2 # Copyright (c) 2014 The Chromium Authors. All rights reserved.	2 # Copyright (c) 2014 The Chromium Authors. All rights reserved.

3 # Use of this source code is governed by a BSD-style license that can be	3 # Use of this source code is governed by a BSD-style license that can be

4 # found in the LICENSE file.	4 # found in the LICENSE file.

5	5

6 NEW_BRANCH=${1?Must supply new branch name as first argument}	6 . ${0/%$(basename "$0")/python_git_runner.sh} \| less -R

7 git checkout --track -b "$NEW_BRANCH"

OLD	NEW

« no previous file with comments | « no previous file | git-nav-downstream » ('j') | git_common.py » ('J')