Skip to content
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

Better README #383

Closed
wants to merge 4 commits into from
Closed

Conversation

vickysharma0812
Copy link
Contributor

Pull request purpose

related to issue #382, and enhancement in documentation.

Detailed changes proposed in this pull request

  • README file in markdown form
  • Please check the headings

README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
@fghoussen
Copy link
Collaborator

What is the purpose of install.sh?

@vickysharma0812
Copy link
Contributor Author

Please ignore it. It is for me to install ARPACK for my development.

@fghoussen
Copy link
Collaborator

Can you had commits for each remark above (easier to follow-up) before merging.

Please ignore it. It is for me to install ARPACK for my development.

I can't, you added it in the PR: please, revert it or push-force.

@vickysharma0812
Copy link
Contributor Author

@fghoussen I have deleted the install.sh. Is there anything pending from myside?

@fghoussen
Copy link
Collaborator

fghoussen commented Dec 22, 2022

@fghoussen I have deleted the install.sh. Is there anything pending from myside?

@vickysharma0812: Yes, can you had 1 commit for each remark (easier to follow-up) I made in the review before merging.

README.md Outdated Show resolved Hide resolved
@fghoussen
Copy link
Collaborator

@vickysharma0812: Yes, can you had 1 commit for each remark (easier to follow-up) I made in the review before merging.

vickysharma0812 and others added 4 commits January 27, 2023 19:30
@fghoussen
Copy link
Collaborator

We are about to create a new release #394: @vickysharma0812, do you want to finish this PR (#383 (comment))? If not now, will be for next release.

@vickysharma0812
Copy link
Contributor Author

We are about to create a new release #394: @vickysharma0812, do you want to finish this PR (#383 (comment))? If not now, will be for next release.

Honestly speaking, I am confused about what should I do. Can you please tell me, I am sorry for the inconvenience.

@fghoussen
Copy link
Collaborator

Honestly speaking, I am confused about what should I do. Can you please tell me, I am sorry for the inconvenience.

You proposed a PR to make README more readable. Before merging, I asked you to apply several modifications (example: #383 (comment)) you reacted to 👍 : now, you should add 1 commit for each remark above (the last one behing #383 (comment)).

Also please rebase your PR branch on master

@fghoussen
Copy link
Collaborator

@vickysharma0812: just realized you add modifications. Missed that, sorry.
All has been merged in #397

@fghoussen fghoussen closed this Feb 11, 2023
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.

3 participants