Do not tell people to ask me for help. I won't help them.

Do not tell people to ask me for help. I won't help them.

Write a small HowTo to help confused people by confusing checks.

R=iannucci@chromium.org
BUG=

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=244717

[iannucci, 2014-01-14 02:38:39]

lgtm % english :)

https://codereview.chromium.org/137653003/diff/1/presubmit_support.py
File presubmit_support.py (right):

https://codereview.chromium.org/137653003/diff/1/presubmit_support.py#newcode...
presubmit_support.py:1306: 'to figure out the PRESUBMIT.py which were run, then
run git blame\n'
to figure out which PRESUBMIT.py was run, ...

[Dirk Pranke, 2014-01-14 03:11:01]

I would be tempted to delete this message altogether. I've almost never seen a
case where the presubmit warnings were wrong *and* it wasn't fairly clear to me
what to do about it, so this has always just been noise to me. 

However, if you've gotten enough questions over the years such that you think
it's worth it to still have something, that's fine by me.

[M-A Ruel, 2014-01-14 15:19:50]

I'll commit manually because Rietveld HTTP 500s while uploading.

On 2014/01/14 03:11:01, Dirk Pranke wrote:
> I would be tempted to delete this message altogether. I've almost never seen a
> case where the presubmit warnings were wrong *and* it wasn't fairly clear to
me
> what to do about it, so this has always just been noise to me. 
> 
> However, if you've gotten enough questions over the years such that you think
> it's worth it to still have something, that's fine by me.

You should put your email address then! :)

Lack of signal is not a signal. It's not because people do not ask on
chromium-dev@ that they are not confused. This quick how to will help with the
most common cases.

https://codereview.chromium.org/137653003/diff/1/presubmit_support.py
File presubmit_support.py (right):

https://codereview.chromium.org/137653003/diff/1/presubmit_support.py#newcode...
presubmit_support.py:1306: 'to figure out the PRESUBMIT.py which were run, then
run git blame\n'
On 2014/01/14 02:38:39, iannucci wrote:
> to figure out which PRESUBMIT.py was run, ...

Done.

[M-A Ruel, 2014-01-14 15:23:03]

Committed patchset #3 manually as r244717.