Skip to content

bump tetgen commit hash#1815

Merged
alecjacobson merged 2 commits intomainfrom
bump-tetgen
May 26, 2021
Merged

bump tetgen commit hash#1815
alecjacobson merged 2 commits intomainfrom
bump-tetgen

Conversation

@alecjacobson
Copy link
Copy Markdown
Contributor

tetgen commit hash was pointing to the wrong repo. Meanwhile, tetgen has released a new version, now mirrored in https://github.com/libigl/tetgen

GIT_REPOSITORY https://github.com/jdumas/tetgen.git
GIT_TAG c63e7a6434652b8a2065c835bd9d6d298db1a0bc
GIT_REPOSITORY https://github.com/libigl/tetgen.git
GIT_TAG 6407f3962d4e24426a81955664391da74e2e2311
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Where did you get this SHA1 from? I don't see it in our tetgen mirror.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

it's in the v16 branch. The commit hash should be the same when that's merged.

@jdumas
Copy link
Copy Markdown
Collaborator

jdumas commented May 26, 2021

I already fixed this as part of #1805. I would rather avoid creating file conflicts with that PR, and focus on reviewing/merging #1805 instead...

@alecjacobson
Copy link
Copy Markdown
Contributor Author

I already fixed this as part of #1805. I would rather avoid creating file conflicts with that PR, and focus on reviewing/merging #1805 instead...

I think you fixed the wrong repo thing but it's still pointing to the out-of-date version of tetgen.

@jdumas
Copy link
Copy Markdown
Collaborator

jdumas commented May 26, 2021

Oh I didn't see TetGen had a new version 1.6 released in 2020... What a time to live it. Let's merge your 1.6 branch onto the main tetgen branch first then. Then we should update the SHA1 in #1805 directly.

@alecjacobson alecjacobson merged commit 46b9ab8 into main May 26, 2021
@alecjacobson alecjacobson deleted the bump-tetgen branch May 26, 2021 17:57
@jdumas jdumas added this to the v3.0.0 milestone May 26, 2021
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