-
-
Notifications
You must be signed in to change notification settings - Fork 360
Euler fortran #411
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
Euler fortran #411
Conversation
This is how I would do it, assuming that you have git fetch --all
git checkout euler_fortran
git rebase -i upstream/master This allows you to do an interactive rebase of your branch on top of the current master, so you can change anything in your history. The option I would take is to rewrite the commit message of the first commit to make sense, then "fixup" all other later commits into that one. It squashes everything but discards commit messages. Compare this to when we hit "Squash and merge" on GitHub, which will pack everything into a single commit just fine, but keep all the nonsense commit messages. |
I think this is a good PR. Quick question about the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Clean fortran implementation. I am happy with it.
* Delete monte_carlo_pi.f90 * init * further implementation * next * forward euler implementation * revoked merge changed from bubble.f90 * Gitbook documentation * fix fortran highlight
Hey all!
Another Fortran implementation done.
Compiled without erros with
gcc-Version 8.2.1 20180831 (GCC)
usinggfortran -Og -Wall -Werror -std=f95 -fimplicit-none euler.f90 -o euler
.Something odd with my git again. The merge history is shown. Any idea how to resolve this even though it does not collide with AAA's master branch?
Regards
depate