-
Notifications
You must be signed in to change notification settings - Fork 8
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
Branches #14
Comments
Another issue: There are some files in which use the removed files from unsupported.. Is it easy to update these ? |
The two extra branches contain files/features from the old gsElasticity which I would like to include into the master branch but for which I haven't had time yet. Meanwhile, I would like to keep the master branch clean. Regarding the files in motor/unikl: some are already transferred to gsElasticity/example. I can move the rest to the gsElasticity/elastToDo branch and rework them later. I don't think it makes sense to keep them in the motor submodule since they can't be compiled now that gsElasticity is removed from the unsupported submodule. And making motor/unikl dependant on an external submodule (gsElasticity) is probably a bad idea. What do you think? |
Hi Angelos, this conversation has become a bit inactive. Are we still going to make gsElasticity public? The core is functional and I keep working on further features |
there are 2 extra branches in gsElasticity.
Do we still need the other 2?
if yes, maybe we should merge stable in them ?
if no, we delete them ?
The text was updated successfully, but these errors were encountered: