Merge changes for #221 into "main"

[nacl]

Includes the fixes from #221 into the new "main" branch. It was previously committed to the "master" branch.

[googlebot]

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).

📝 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.

[aiuto]

We may need @davschne to resend the PR to the main branch. Or just redo the change without attribution.

[davschne]

I'll redo my PR. Sorry about that; I assumed master was the default branch. For my future understanding, what's the role of master in this repository?

[aiuto]

On Tue, Sep 8, 2020 at 5:00 PM David Schneider ***@***.***> wrote: I'll redo my PR. Sorry about that; I assumed master was the default branch.

Not your fault. The change was easy to miss unless you read every issue and PR.

For my future understanding, what's the role of master in this repository?

I renamed master to main about a month ago. #199 Everyone should rename their master branches to main if they have work in progress. In the future, I will try harder to check that PRs are not against master. —

…

You are receiving this because your review was requested. Reply to this email directly, view it on GitHub <#229 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAXHHHE2BQX4BBG5Y4XQSKDSE2LP5ANCNFSM4QZILPIQ> .

[davschne]

Thanks for the clarification, @aiuto.

Here's a new PR targeting main: #230

I rebased onto current HEAD of main, so it's a new commit with the same content.

[nacl]

Obviated by #230. Thanks!