git cl upload: print patchset when uploading to Rietvled.

git cl upload: print patchset when uploading to Rietvled.

R=andybons@chromium.org,phajdan@chromium.org
BUG=

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=299174

[tandrii(chromium), 2016-03-08 18:33:23]

PTAL

Example output:

# Creating issue - first patchset

$ git cl upload
Using 50% similarity for rename/copy detection. Override with --similarity.
 third_party/upload.py | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)
Upload server: https://codereview.chromium.org (change with -s/--server)
Issue created. URL: https://codereview.chromium.org/1772293003 (patchset: 1)
Uploading base file for third_party/upload.py

# Updating:
$ git cl upload
Using 50% similarity for rename/copy detection. Override with --similarity.
 third_party/upload.py | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)
This branch is associated with issue 1772293003. Adding patch to that issue.
Upload server: https://codereview.chromium.org (change with -s/--server)
Issue updated. URL: https://codereview.chromium.org/1772293003 (patchset: 20001)



Motivation:
 I want to know which PS to try on command line.

FTR, upload.py <-> Rietveld is just insane protocol - it's parsing human
readable raw text!

[tandrii(chromium), 2016-03-08 18:33:35]

Description was changed from

==========
git cl upload: print patchset when uploading to Rietvled.

R=andybons@chromium.org,phajdan@chromium.org
BUG=
==========

to

==========
git cl upload: print patchset when uploading to Rietvled.

R=andybons@chromium.org,phajdan@chromium.org
BUG=
==========

[tandrii(chromium), 2016-03-08 18:33:35]

tandrii@chromium.org changed reviewers:
+ phajdan.jr@chromium.org
- phajdan@chromium.org

[Bons, 2016-03-08 18:48:22]

lgtm

https://codereview.chromium.org/1772293003/diff/20001/third_party/upload.py
File third_party/upload.py (right):

https://codereview.chromium.org/1772293003/diff/20001/third_party/upload.py#n...
third_party/upload.py:2505: assert issue
this is meant to be in here?

[tandrii(chromium), 2016-03-08 19:02:47]

https://codereview.chromium.org/1772293003/diff/20001/third_party/upload.py
File third_party/upload.py (right):

https://codereview.chromium.org/1772293003/diff/20001/third_party/upload.py#n...
third_party/upload.py:2505: assert issue
On 2016/03/08 18:48:22, Bons wrote:
> this is meant to be in here?

Yes, as I slightly changed logical conditions from previous versions. Thus,
while i am 99% certain my change is OK, this assert will help find the CL in the
event that I am wrong.

[Paweł Hajdan Jr., 2016-03-08 23:53:20]

LGTM

[tandrii(chromium), 2016-03-09 06:59:46]

The CQ bit was checked by tandrii@chromium.org

[commit-bot: I haz the power, 2016-03-09 06:59:50]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1772293003/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1772293003/20001

[commit-bot: I haz the power, 2016-03-09 07:01:57]

Description was changed from

==========
git cl upload: print patchset when uploading to Rietvled.

R=andybons@chromium.org,phajdan@chromium.org
BUG=
==========

to

==========
git cl upload: print patchset when uploading to Rietvled.

R=andybons@chromium.org,phajdan@chromium.org
BUG=

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=299174
==========

[commit-bot: I haz the power, 2016-03-09 07:01:58]

Committed patchset #2 (id:20001) as
http://src.chromium.org/viewvc/chrome?view=rev&revision=299174