Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix int64_t_t typo in README code example #3

Merged
merged 1 commit into from Jan 15, 2014
Merged

Fix int64_t_t typo in README code example #3

merged 1 commit into from Jan 15, 2014

Conversation

sashasochka
Copy link
Contributor

Fixes a typo where the first type was written as int64_t_t with suffixing _t twice and the second type misses suffix at all.

Fixes a typo where the first type was written as int64_t_t with suffixing _t twice and the second type misses suffix at all.
dmah42 pushed a commit that referenced this pull request Jan 15, 2014
Fix int64_t_t typo in README code example
@dmah42 dmah42 merged commit 6df14ae into google:master Jan 15, 2014
@pphaneuf
Copy link
Contributor

pphaneuf commented Feb 4, 2014

It appears @sochka has not signed the CLA (contributor license agreement)? I'm a bit new to this here, so I might be wrong, but you'd be looking at one of the following two, as appropriate:

https://developers.google.com/open-source/cla/individual
https://developers.google.com/open-source/cla/corporate

@pphaneuf
Copy link
Contributor

pphaneuf commented Feb 4, 2014

To be clear, let us know as soon as you signed it, we'll check it's good on our side and re-integrate your commit. This is just a minor administrative setback, sorry about that.

@sashasochka
Copy link
Contributor Author

Well, looks like there is quite a bit of bureaucracy in Google too if there is a need in signing two docs for fixing just a single typo)

Ok, what do I put at https://developers.google.com/open-source/cla/corporate as my corporation name if I'm a student? Just leave it blank?

@dmah42
Copy link
Member

dmah42 commented Feb 4, 2014

You only need to sign one of them, I believe. Use the individual CLA.

@pphaneuf
Copy link
Contributor

pphaneuf commented Feb 4, 2014

Oh, you just need to pick the appropriate one! If you're a student, I think you should use the individual version.

This is unfortunately needed to ensure license compliance, for both you and us. As mentioned, I'm a bit new to this myself, and I'm trying to find out if there can be an exception for a small typo fix, but it is simpler/safer if you simply sign the CLA (it also applies to most other Google open source project). :-)

@sashasochka
Copy link
Contributor Author

Oh, sorry. I've already signed the first one.

@pphaneuf
Copy link
Contributor

pphaneuf commented Feb 4, 2014

No problem, thank you! I'm putting back your contribution immediately.

dmah42 pushed a commit that referenced this pull request May 17, 2021
GerHobbelt pushed a commit to GerHobbelt/benchmark that referenced this pull request Mar 20, 2024
GerHobbelt pushed a commit to GerHobbelt/benchmark that referenced this pull request Mar 20, 2024
The premake build structure has been simplified and rewritten to reduce
the boilerplate needed to add additional configurations while forcing
the unique settings of a project to be defined. Migrate some defines
and compiler options to the global settings and remove all the old
boilerplate from this project.

Issue-number: https://devtopia.esri.com/runtime/devops/issues/830
Signed-off-by: Christian O. Venegas <cvenegas@esri.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants