Add SVI example documentation
- (M) doc/network_instance_examples.md
- Add switch router hybrid Routed Vlan example
resolves https://github.com/openconfig/public/issues/354 as well as some others perhaps. Please advise on best way to approach documenting some of these types of questions in issues / the mailer
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
:memo: Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.
What to do if you already signed the CLA
Individual signers
- It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.
Corporate signers
- Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
- The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
- The email used to register you as an authorized contributor must also be attached to your GitHub account.
ℹ️ Googlers: Go here for more info.
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
:memo: Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.
What to do if you already signed the CLA
Individual signers
- It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.
Corporate signers
- Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
- The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
- The email used to register you as an authorized contributor must also be attached to your GitHub account.
ℹ️ Googlers: Go here for more info.
Compatibility Report for commit 9f7bc4d3e96a736929e2a755c8a5532b041655c5: ⛔ yanglint@SO 1.7.11
@googlebot I signed it!
@aashaikh @robshakir 👋 First commits to this organization , any advice or steering greatly appreciated !
Thanks for the contribution here, and apologies for the review delay :-(
I'm reviewing this and will discuss it tomorrow with the wider group.
/gcbrun
No major YANG version changes in commit 894dadfb421799bda9b153a1bebb37d5fda07796
@eth0xFEED this LGTM, can you re-check your CLA? Sorry but you might need to re-register.
@eth0xFEED this LGTM, can you re-check your CLA? Sorry but you might need to re-register.
Hi @eth0xFEED still looking for the CLA to be signed.
/gcbrun