Switch jsoncpp DEPS to github mirror

Switch jsoncpp DEPS to github mirror

This change should be no-op.  It simply changes the sha1
for jsoncpp to match the commit in the github repo rather
than the git-svn mirror we previously used.  The sha1
differs simply because the git-svn metadata was not used
when they migrated to github. The tree contents are
identical (the two commits have the same tree sha1).

BUG=472809
Committed: https://crrev.com/12f9e9d69d223afd5c30dad8934932aefdeba35e
Cr-Commit-Position: refs/heads/master@{#324477}

[Sam Clegg, 2015-04-07 21:59:47]

sbc@chromium.org changed reviewers:
+ iannucci@chromium.org

[Sam Clegg, 2015-04-07 21:59:47]

BTW, this makes the following mirrors unused:

external/jsoncpp	
external/jsoncpp/jsoncpp	
external/jsoncpp/jsoncpp/include	
external/jsoncpp/jsoncpp/src/lib_json

Is there some way to hide them, or marked as redundant/legacy?

[Sam Clegg, 2015-04-08 21:33:16]

ping.. (did you see this Robbie?)

[iannucci, 2015-04-08 21:47:15]

lgtm

[Sam Clegg, 2015-04-08 22:11:01]

The CQ bit was checked by sbc@chromium.org

[commit-bot: I haz the power, 2015-04-08 22:12:18]

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

[Sam Clegg, 2015-04-09 00:28:21]

sbc@chromium.org changed reviewers:
+ pthatcher@chromium.org

[Sam Clegg, 2015-04-09 00:28:22]

+pthatcher for jsoncpp/OWNERS, sorry should have looped you in earlier.

[Sam Clegg, 2015-04-09 00:30:02]

On 2015/04/09 00:28:22, Sam Clegg wrote:
> +pthatcher for jsoncpp/OWNERS, sorry should have looped you in earlier.

For a bit of background, my long term goal is to roll jsoncpp and this is an
intermediate CL since jsoncpp is now being developed on github.

[commit-bot: I haz the power, 2015-04-09 03:19:43]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-04-09 03:19:46]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[pthatcher2, 2015-04-09 05:41:51]

Honestly, I don't even know how I became an OWNER (or, as it appears, THE
owner).  I don't know anything about jsoncpp, other than two small parts of
WebRTC (which I do work on) depend on it.  

Who is going to be regularly rolling it?  Shouldn't that person by an OWNER (or
THE owner)?

[Sam Clegg, 2015-04-09 16:50:01]

OK, we use this is the NaCl SDK, so I've added myself as an OWNER.

PTAL.

[Sam Clegg, 2015-04-09 16:50:13]

The CQ bit was checked by sbc@chromium.org to run a CQ dry run

[Sam Clegg, 2015-04-09 16:50:14]

The patchset sent to the CQ was uploaded after l-g-t-m from
iannucci@chromium.org
Link to the patchset: https://codereview.chromium.org/1069163002/#ps40001
(title: " ")

[commit-bot: I haz the power, 2015-04-09 16:50:33]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1069163002/40001

[pthatcher2, 2015-04-09 16:55:04]

lgtm

[commit-bot: I haz the power, 2015-04-09 18:16:21]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-04-09 18:16:22]

This issue passed the CQ dry run.

[Sam Clegg, 2015-04-09 18:17:12]

The CQ bit was checked by sbc@chromium.org

[commit-bot: I haz the power, 2015-04-09 18:18:14]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1069163002/40001

[commit-bot: I haz the power, 2015-04-09 18:20:21]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2015-04-09 18:21:16]

Patchset 3 (id:??) landed as
https://crrev.com/12f9e9d69d223afd5c30dad8934932aefdeba35e
Cr-Commit-Position: refs/heads/master@{#324477}