Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(16)

Issue 542007: Fixed issue with try where patchset is passed.... (Closed)

Created:
10 years, 11 months ago by Mohamed Mansour
Modified:
9 years, 6 months ago
Reviewers:
M-A Ruel
CC:
chromium-reviews_googlegroups.com, M-A Ruel
Visibility:
Public.

Description

Fixed issue with try where patchset is passed. The new try execution should only be triggered when a user just passes the rietveld issue number. Usually, if your branch has a working patchset already defined, it shouldn't think the user passed it. The code has been updated to force patchset to be None (not 0 or any other number) so that specific occurence wont happen again. TBR=maruel BUG=None TEST=git try, git try --issue=123, git try --issue=123 --patchset=0, should all work fine now. Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=35889

Patch Set 1 #

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

Powered by Google App Engine
This is Rietveld 408576698