Do not interfere with git cl patch <issue>

Do not interfere with git cl patch <issue>

R=dpranke@chromium.org
BUG=
TEST=

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

[Dirk Pranke, 2011-07-25 19:06:54]

http://codereview.chromium.org/7493050/diff/1/presubmit_canned_checks.py
File presubmit_canned_checks.py (right):

http://codereview.chromium.org/7493050/diff/1/presubmit_canned_checks.py#newc...
presubmit_canned_checks.py:70: # If patchset is None, it's likely a patchset in
issue.
I don't follow this comment?

[M-A Ruel, 2011-07-25 19:10:01]

http://codereview.chromium.org/7493050/diff/1/presubmit_canned_checks.py
File presubmit_canned_checks.py (right):

http://codereview.chromium.org/7493050/diff/1/presubmit_canned_checks.py#newc...
presubmit_canned_checks.py:70: # If patchset is None, it's likely a patchset in
issue.
On 2011/07/25 19:06:54, Dirk Pranke wrote:
> I don't follow this comment?

That's normal, it didn't make sense either. Fixed.

[Dirk Pranke, 2011-07-25 21:03:15]

http://codereview.chromium.org/7493050/diff/5001/presubmit_canned_checks.py
File presubmit_canned_checks.py (right):

http://codereview.chromium.org/7493050/diff/5001/presubmit_canned_checks.py#n...
presubmit_canned_checks.py:72: # by a committer to be checked-in.
Okay, I follow the comment this time, but it is a bit confusing because you're
referencing the 'patchset' field in the comment, but not in the code; this would
lead the reader wonder why you were mentioning it at all. Perhaps just delete
the comment altogether?

[M-A Ruel, 2011-07-26 00:28:18]

done

[Dirk Pranke, 2011-07-26 00:29:48]

LGTM.