Skip to content
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

Digest Support: init first connection with null headers #431

Merged
merged 2 commits into from
Mar 11, 2019
Merged

Digest Support: init first connection with null headers #431

merged 2 commits into from
Mar 11, 2019

Conversation

mssfang
Copy link
Member

@mssfang mssfang commented Feb 25, 2019

Description

This checklist is used to make sure that common guidelines for a pull request are followed.

  • I have read the contribution guidelines.
  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR.
  • The pull request does not introduce breaking changes (unless a major version change occurs in the assembly and module).
  • If applicable, the public code is properly documented.
  • Pull request includes test coverage for the included changes.
  • The code builds without any errors.

@mssfang
Copy link
Member Author

mssfang commented Mar 11, 2019

Hi, James,

Can you merge this PR which corresponds to the proton-j-extension PR[https://github.com/Azure/qpid-proton-j-extensions/pull/10]

Thank you,
Shawn

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants