Adding Venafi 2nd Gen CT Log

Adding Venafi 2nd Gen CT Log

Add the information about the Venafi 2nd generation CT log that
recently passed compliance.

This is a merge of the data approved in:
https://bugs.chromium.org/p/chromium/issues/detail?id=688510#c18

It is not possible, unfortunately, to simply cherry-pick the original
change (https://codereview.chromium.org/2874423002) because it depends
on another change to operate correctly
(https://chromium.googlesource.com/chromium/src/+/9657f6767718da315773bef39143c869508becc3), so cherry-picking fails.

BUG=688510
R=rsleevi@chromium.org

Review-Url: https://codereview.chromium.org/2898173002 .
Cr-Commit-Position: refs/branch-heads/3071@{#682}
Cr-Branched-From: a106f0abbf69dad349d4aaf4bcc4f5d376dd2377-refs/heads/master@{#464641}
Committed: https://chromium.googlesource.com/chromium/src/+/519cff3570d4f9bc6e0041161c3bd9947218a5b7

[Eran Messeri, 2017-05-23 13:54:09]

Description was changed from

==========
Adding Venafi 2nd Gen CT Log

Add the information about the Venafi 2nd generation CT log that
recently passed compliance.

This is a merge of the data approved in:
https://bugs.chromium.org/p/chromium/issues/detail?id=688510#c18

It is not possible, unfortunately, to simply cherry-pick the original
change (https://codereview.chromium.org/2874423002) because it depends
on another change to operate correctly
(https://chromium.googlesource.com/chromium/src/+/9657f6767718da315773bef39143...),
so cherry-picking fails.

BUG=682193
==========

to

==========
Adding Venafi 2nd Gen CT Log

Add the information about the Venafi 2nd generation CT log that
recently passed compliance.

This is a merge of the data approved in:
https://bugs.chromium.org/p/chromium/issues/detail?id=688510#c18

It is not possible, unfortunately, to simply cherry-pick the original
change (https://codereview.chromium.org/2874423002) because it depends
on another change to operate correctly
(https://chromium.googlesource.com/chromium/src/+/9657f6767718da315773bef39143...),
so cherry-picking fails.

BUG=688510
==========

[Eran Messeri, 2017-05-24 08:50:59]

eranm@chromium.org changed reviewers:
+ rsleevi@chromium.org

[Eran Messeri, 2017-05-24 08:57:41]

Ryan, could you please review and make sure I'm landing the right thing on the
right place?

I've produced the patch by doing:
git checkout remotes/branch-heads/3071 <- Ended up in detached HEAD state
git checkout -b my_m59_branch
hacking net/cert/ct_known_logs_static-inc.h
git commit -a

Then:
git-cl upload --target_branch=refs/branch-heads/3071 HEAD^

I just want to confirm that when I do git-cl land I land it on the right branch.
I got the branch number from the bug.

[Ryan Sleevi, 2017-05-24 13:51:01]

LGTM

You should be good to "git cl land" now

[Eran Messeri, 2017-05-24 13:56:05]

Description was changed from

==========
Adding Venafi 2nd Gen CT Log

Add the information about the Venafi 2nd generation CT log that
recently passed compliance.

This is a merge of the data approved in:
https://bugs.chromium.org/p/chromium/issues/detail?id=688510#c18

It is not possible, unfortunately, to simply cherry-pick the original
change (https://codereview.chromium.org/2874423002) because it depends
on another change to operate correctly
(https://chromium.googlesource.com/chromium/src/+/9657f6767718da315773bef39143...),
so cherry-picking fails.

BUG=688510
==========

to

==========
Adding Venafi 2nd Gen CT Log

Add the information about the Venafi 2nd generation CT log that
recently passed compliance.

This is a merge of the data approved in:
https://bugs.chromium.org/p/chromium/issues/detail?id=688510#c18

It is not possible, unfortunately, to simply cherry-pick the original
change (https://codereview.chromium.org/2874423002) because it depends
on another change to operate correctly
(https://chromium.googlesource.com/chromium/src/+/9657f6767718da315773bef39143...),
so cherry-picking fails.

BUG=688510
R=rsleevi@chromium.org

Review-Url: https://codereview.chromium.org/2898173002 .
Cr-Commit-Position: refs/branch-heads/3071@{#682}
Cr-Branched-From:
a106f0abbf69dad349d4aaf4bcc4f5d376dd2377-refs/heads/master@{#464641}
Committed:
https://chromium.googlesource.com/chromium/src/+/519cff3570d4f9bc6e0041161c3b...
==========

[Eran Messeri, 2017-05-24 13:56:06]

Committed patchset #2 (id:20001) manually as
519cff3570d4f9bc6e0041161c3bd9947218a5b7 (presubmit successful).

[Eran Messeri, 2017-05-24 13:57:39]

Thanks, Ryan!

for posterity, I'd had to:
git branch --set-upstream-to branch-heads/3071

before git-cl landing the change, since otherwise it complained about many
commits in the base branch that are not in this branch.