Github user JemDay commented on the issue:
https://github.com/apache/qpid-proton/pull/75
i think this is royally screwed up now, the file-change list looks clean
but using a rebase rather than a pull (to remove the merge commits) now appears
to be having an even worse affect.
I'm open to suggestions - i can close this PR, trash my fork, and then
re-create the change if that's going to be a simpler path forward but before
that i would like to better understand the fork/pull/commit/push/PR cycle when
there may be multiple commits to the fork before the PR is actually raised.
Squashing after commits have been pushed seems to just open world of hurt
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
