-
Notifications
You must be signed in to change notification settings - Fork 57
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
Made changes to highest #5
base: obliv-c
Are you sure you want to change the base?
Conversation
Change (&) to (&&) in line 287
Starting a test branch
Update README.md
Thanks. About cleaning up commit logs before pushing, yes there is a way, but it takes a bit more work. You can get started by reading through this page about git: http://git-scm.com/book/en/Git-Internals-Git-References Essentially the workflow looks like this (remember that branches are super cheap in git):
If you want, you can practice doing this right here using these commits. If you have already done your work on the main branch (I think it's called |
I made the changes to highest, and everything still works exactly like it is supposed to.
Is there anyway that I can separate all of the commits from each other at a pull request so that you don't have to accept all of these at once?
In here is also what we have been working on this week, which is the Private Set Intersection