Issue 555183: Fix for git-svn rebase bug

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

Issue 555183: Fix for git-svn rebase bug (Closed)

Created:
10 years, 10 months ago by Nasser Grainawi

Modified:
9 years, 7 months ago

Reviewers:
M-A Ruel

CC:
chromium-reviews_googlegroups.com, M-A Ruel

Visibility:
Public.

Description

Fix for git-svn rebase bug git-svn rebase will always output 'Current branch <> is up-to-date' when the branch is up-to-date, even if you pass the --quiet flag(s). This change specifically squelches that message. Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=37696

Patch Set 1 #

Created: 10 years, 10 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+5 lines, -1 line)			Patch
	M	gclient	View		1 chunk	+5 lines, -1 line	0 comments	Download

Messages

Total messages: 2 (0 generated)

Expand Messages | Collapse Messages

M-A Ruel

10 years, 10 months ago (2010-01-30 02:42:35 UTC) #2

Don't know bash much but lgtm.

I'm just wondering what happens if git-svn prompts for credential but it should
be a rare case enough that it's not worth bothering.

Expand Messages | Collapse Messages