GitHub user astitcher opened a pull request:

    https://github.com/apache/qpid-proton/pull/87

    Proton-c core split

    This is mostly for comment by @alanconway and @cliffjansen.
    
    It is a rearrangement of the Proton-c source tree, and an introduction of a 
core OS and IO independent qpid-proton-core library.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/astitcher/qpid-proton proton-core

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/qpid-proton/pull/87.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #87
    
----
commit 82a590e7cf8d8c9f16e66282703b0e5fc8b3c3e3
Author: Andrew Stitcher <[email protected]>
Date:   2016-08-30T20:36:19Z

    PROTON-1350 PROTON-1351: Introduce proton-c core library
    - Created new core proton library qpid-proton-core which only contains
      protocol processsing and no IO.
    - Rearranged source tree to separate core protocol code and 
io/reactor/extra code
    - Rearranged code so that compiler dependent code is isolated and platform 
(OS)
      dependent code is isolated
    
    This is a large change, but the majority is moving files around and fixing 
up the header
    includes. There is a small amount of internal API changing so support the 
core searation.

commit 8336cd284b273fa5395c9424d05ae9bb36ae081e
Author: Andrew Stitcher <[email protected]>
Date:   2016-10-10T19:32:15Z

    Make go binding only depend on qpid-proton-core

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to