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

Update doxygen for LIE fracture models. #1971

Merged
merged 8 commits into from Oct 27, 2017

Conversation

Projects
None yet
3 participants
@endJunction
Member

endJunction commented Oct 26, 2017

This is almost the same as #1968 but without spurious files and less doxygen errors. (Yes there were some...)

endJunction added some commits Oct 18, 2017

[doc] Update fracture models prj file docu.
Especially move to fracture_model folder instead of solid/constitutive_relation,
Use a symbolic link to point to fracture models from LIE processes.
[doc] Remove redundant c_process.md.
Having i_process.md and c_process.md results in an index listing all
processes twice.

@endJunction endJunction force-pushed the endJunction:UpdateDoxygenDocu branch from 3e1ac31 to c0acdc9 Oct 27, 2017

@endJunction endJunction force-pushed the endJunction:UpdateDoxygenDocu branch from c0acdc9 to 4c46d0d Oct 27, 2017

@endJunction endJunction merged commit 8bf05da into ufz:master Oct 27, 2017

2 of 3 checks passed

continuous-integration/jenkins/pr-merge This commit cannot be built
Details
continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details

@endJunction endJunction deleted the endJunction:UpdateDoxygenDocu branch Oct 27, 2017

@renchao-lu

This comment has been minimized.

Contributor

renchao-lu commented on bbbfc91 Nov 6, 2017

Perhaps project files (e.g. single_joint.prj) need to be updated accordingly. Do you have time to update? If not, I can do it as well. @endJunction

This comment has been minimized.

Member

endJunction replied Nov 6, 2017

This is already changed in the ufz/ogs-data@a9f0365

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment