Add a Yo Dawg to wake up folks.

Add a Yo Dawg to wake up folks.

Some people just don't want to read chromium-dev@. Wake them up.

R=iannucci@chromium.org
BUG=

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

[iannucci, 2013-11-15 22:02:22]

https://codereview.chromium.org/74273002/diff/1/git-try
File git-try (right):

https://codereview.chromium.org/74273002/diff/1/git-try#newcode14
git-try:14: echo ''
Hm, aren't there some lingering legitimate uses for git try?

[M-A Ruel, 2013-11-15 22:06:15]

relatively speaking

https://codereview.chromium.org/74273002/diff/1/git-try
File git-try (right):

https://codereview.chromium.org/74273002/diff/1/git-try#newcode14
git-try:14: echo ''
On 2013/11/15 22:02:22, iannucci wrote:
> Hm, aren't there some lingering legitimate uses for git try?

Yes but not many.

[iannucci, 2013-11-15 22:10:43]

On 2013/11/15 22:06:15, M-A Ruel wrote:
> relatively speaking
> 
> https://codereview.chromium.org/74273002/diff/1/git-try
> File git-try (right):
> 
> https://codereview.chromium.org/74273002/diff/1/git-try#newcode14
> git-try:14: echo ''
> On 2013/11/15 22:02:22, iannucci wrote:
> > Hm, aren't there some lingering legitimate uses for git try?
> 
> Yes but not many.

Could we whitelist legitimate base urls maybe? Or blacklist known-silly uses
(like single-repo patches to src or third_party/WebKit?)

[M-A Ruel, 2013-11-15 22:21:12]

> > On 2013/11/15 22:02:22, iannucci wrote:
> > > Hm, aren't there some lingering legitimate uses for git try?
> > 
> > Yes but not many.
> 
> Could we whitelist legitimate base urls maybe? Or blacklist known-silly uses
> (like single-repo patches to src or third_party/WebKit?)

I can revert it after a month if this concerns you. It's really just outputting
an additional string.

[iannucci, 2013-11-15 22:25:04]

On 2013/11/15 22:21:12, M-A Ruel wrote:
> > > On 2013/11/15 22:02:22, iannucci wrote:
> > > > Hm, aren't there some lingering legitimate uses for git try?
> > > 
> > > Yes but not many.
> > 
> > Could we whitelist legitimate base urls maybe? Or blacklist known-silly uses
> > (like single-repo patches to src or third_party/WebKit?)
> 
> I can revert it after a month if this concerns you. It's really just
outputting
> an additional string.

Yeah I know, I just don't want to falsely bug the legitimate users.

lgtm. If someone complains I've got you on speed dial ;-P

[commit-bot: I haz the power, 2013-11-17 20:12:42]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/maruel@chromium.org/74273002/1

[commit-bot: I haz the power, 2013-11-17 20:14:17]

Change committed as 235548

[cmp, 2013-11-26 17:53:26]

I sympathize with wanting to move people over to git cl try, however the
legitimate uses of git try make this message confusing for those groups and ends
up adding noise for them.  We should revert this until there is a better
solution to pursue.

[M-A Ruel, 2013-11-26 17:54:33]

On 2013/11/26 17:53:26, cmp wrote:
> I sympathize with wanting to move people over to git cl try, however the
> legitimate uses of git try make this message confusing for those groups and
ends
> up adding noise for them.  We should revert this until there is a better
> solution to pursue.

I was planning to revert this next week.

[scottmg, 2013-11-26 23:27:34]

On 2013/11/26 17:54:33, M-A Ruel wrote:
> On 2013/11/26 17:53:26, cmp wrote:
> > I sympathize with wanting to move people over to git cl try, however the
> > legitimate uses of git try make this message confusing for those groups and
> ends
> > up adding noise for them.  We should revert this until there is a better
> > solution to pursue.
> 
> I was planning to revert this next week.

Yeah, it's a bit confusing for, e.g. people working on gyp. I guess
alternatively having "git cl try" work everywhere would be a good fix. :)