Add old UrlFetcher.StringResponseSize histogram to histograms.xml.

Add old UrlFetcher.StringResponseSize histogram to histograms.xml.

BUG=535601
Committed: https://crrev.com/32f7bac51e9d8c92464de0331f9156a8f91d946a
Cr-Commit-Position: refs/heads/master@{#351193}

[mmenke, 2015-09-28 20:27:35]

mmenke@chromium.org changed reviewers:
+ asvitkine@chromium.org

[mmenke, 2015-09-28 20:27:35]

Was about to add a histogram to get this, and then noticed the old one, which
has been around for 3(!) years without anyone looking at it.  :(

[Alexei Svitkine (slow), 2015-09-28 20:58:19]

There's an unknowned version of this in the internal histograms.xml file:
http://cs/chrome/histograms.xml

Could you send a CL removing that one too? Then, I'll stamp both and you can
land them together.

[mmenke, 2015-09-28 21:15:30]

On 2015/09/28 20:58:19, Alexei Svitkine wrote:
> There's an unknowned version of this in the internal histograms.xml file:
> http://cs/chrome/histograms.xml
> 
> Could you send a CL removing that one too? Then, I'll stamp both and you can
> land them together.

Sure.  Is there any documented, fully deterministic process to access the
internal repo?

I stopped checking out chrome-internal when I was unable to figure out how to
check it out after one of the authentication changes...And now it looks like the
location where I would have tried to get it from is now defunct
(https://chrome-internal.googlesource.com/chrome/tools/histograms).

[Alexei Svitkine (slow), 2015-09-28 21:17:47]

On 2015/09/28 21:15:30, mmenke wrote:
> On 2015/09/28 20:58:19, Alexei Svitkine wrote:
> > There's an unknowned version of this in the internal histograms.xml file:
> > http://cs/chrome/histograms.xml
> > 
> > Could you send a CL removing that one too? Then, I'll stamp both and you can
> > land them together.
> 
> Sure.  Is there any documented, fully deterministic process to access the
> internal repo?
> 
> I stopped checking out chrome-internal when I was unable to figure out how to
> check it out after one of the authentication changes...And now it looks like
the
> location where I would have tried to get it from is now defunct
> (https://chrome-internal.googlesource.com/chrome/tools/histograms).

It's no longer in src-internal - now it's in google3 - so it's the same process
as changing e.g. server side experiment configs.

[mmenke, 2015-09-28 21:17:49]

On 2015/09/28 21:15:30, mmenke wrote:
> On 2015/09/28 20:58:19, Alexei Svitkine wrote:
> > There's an unknowned version of this in the internal histograms.xml file:
> > http://cs/chrome/histograms.xml
> > 
> > Could you send a CL removing that one too? Then, I'll stamp both and you can
> > land them together.
> 
> Sure.  Is there any documented, fully deterministic process to access the
> internal repo?
> 
> I stopped checking out chrome-internal when I was unable to figure out how to
> check it out after one of the authentication changes...And now it looks like
the
> location where I would have tried to get it from is now defunct
> (https://chrome-internal.googlesource.com/chrome/tools/histograms).

Oh, it's not in third_party, so I guess that's it's real home now, rather than
it being imported into google3 from elsewhere?  I've never touched google3
before.

[Alexei Svitkine (slow), 2015-09-28 21:28:13]

lgtm

[mmenke, 2015-09-28 21:37:59]

On 2015/09/28 21:28:13, Alexei Svitkine wrote:
> lgtm

Thanks! And thanks for the help!

[mmenke, 2015-09-28 21:38:01]

The CQ bit was checked by mmenke@chromium.org

[commit-bot: I haz the power, 2015-09-28 21:38:58]

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

[commit-bot: I haz the power, 2015-09-28 22:52:54]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-09-28 22:53:53]

Patchset 1 (id:??) landed as
https://crrev.com/32f7bac51e9d8c92464de0331f9156a8f91d946a
Cr-Commit-Position: refs/heads/master@{#351193}