-
Notifications
You must be signed in to change notification settings - Fork 1
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
Added conclave directory with README explaining this fork #2
base: conclave/master
Are you sure you want to change the base?
Conversation
Would it maybe make sense to keep the original readme and just have an additional one for conclave? Now that I think about it, maybe it makes sense to put all of our stuff in it's own directory within the repository. |
The problem then becomes discovery. How does someone new learn how this repo works without being told to open a particular file?
That's the plan. All of the contents of 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.
Minor comments
The patch itself has been applied in a separate PR: #1 |
"Upstream" seems to be standard way to refer to the repo that was forked: https://stackoverflow.com/questions/2739376/definition-of-downstream-and-upstream. |
|
f09538b
to
1dc1e66
Compare
Comments addressed. |
I am not sure why we are doing that. What is the plan to merge graal to repository? Are you doing that as part of another PR? |
I'd suggest dropping a one-two sentence description at the top of the existing readme, and also a link to a readme in the conclave directory. |
Purely to have a separate commit in the git history with just our changes.
I'm not sure what you mean here. But if you're referring to the |
1dc1e66
to
e7d7572
Compare
@ac101m I like your suggestion. Done. |
No description provided.