Skip to content

PR - fix several outstanding PR's without CLA. #132

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

Closed
wants to merge 3 commits into from

Conversation

rsned
Copy link
Collaborator

@rsned rsned commented Mar 28, 2025

ppc64le - Fix deviation in floating point values caused by FMA
Fix godoc url in README.
Fix a few random lint issues.

rsned added 3 commits March 27, 2025 17:32
Fix typos. Fix unneeded cast. Replace loop append with append ... Fix missing compare in a unit test.
@@ -79,7 +79,7 @@ to geography are not part of the core library (e.g. easting/northing
conversions, ellipsoid approximations, geodetic vs. geocentric coordinates,
etc).

See http://godoc.org/github.com/golang/geo for specific package documentation.
See http://pkg.go.dev/github.com/golang/geo for specific package documentation.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Most of this does not match the PR description.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are 3 commits that have gotten smashed together. I'm still trying to figure out the mapping from how easy things worked in g4 to how less intuitive git works. ( I'm still trying to undo a commit == a CL model of things)

This was an attempt to patch in several pull requests that did NOT have CLA so they could be all put in and get closed.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was an attempt to patch in several pull requests that did NOT have CLA so they could be all put in and get closed.

I don't think we can do that.

https://cla.developers.google.com/about/google-individual#:~:text=Should%20You%20wish,party%3A%20%5Bnamed%20here%5D%22.

#91 should be good to merge, if it's really the right solution.

I will try to get the others into shape.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm still trying to figure out the mapping from how easy things worked in g4 to how less intuitive git works. ( I'm still trying to undo a commit == a CL model of things)

You can probably fine some p4/git cheat sheets to help. You might want to try jj, since it's more Mercurial-like.

@rsned rsned changed the title ppc64le - Fix deviation in floating point values caused by FMA PR - fix several outstanding PR's without CLA. Mar 31, 2025
Copy link
Collaborator

@jmr jmr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's get the original PRs submitted instead.

@jmr
Copy link
Collaborator

jmr commented Apr 1, 2025

Fix a few random lint issues.

Which PR is this?

@jmr
Copy link
Collaborator

jmr commented Apr 1, 2025

All PRs have been tickled. I think all but one have a CLA.

@jmr jmr closed this Apr 1, 2025
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.

2 participants