-
Notifications
You must be signed in to change notification settings - Fork 2
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
hpx-parcelport analysis/code review skeleton #4
base: master
Are you sure you want to change the base?
Conversation
provide a skeleton in markdown
create proposal.md
Signed-off-by: Chris Taylor <ct.clmsn@gmail.com>
Signed-off-by: Chris Taylor <ctdotclmsnatgmaildotcom>
Signed-off-by: Chris Taylor <ct(dot)clmsn(at)gmail(dot)com>
@shefty thought i had my DCO conflict issues resolved. will fix later. |
…_controller Signed-off-by: Chris Taylor <ct(dot)clmsn(at)gmail(dot)com>
@ct-clmsn - You may want to look at using stgit (stack git) to manage patch series. It just wraps around raw git commands, but I find it easier to manipulate patches using it. It stores patches in a stack, that you can push and pop onto your tree. This makes it easy to remove patches, adjust one lower down in a series, then push the patches back onto the git tree. So you can fix a patch directly, rather than creating another patch for the same fix. |
this PR should provide interested parties with a sense of what the code analysis will look like going forward. please comment on the PR if there is something missing or if something seems inadequate.