Skip to content
This repository has been archived by the owner on Oct 24, 2022. It is now read-only.

Read response of attempted Sword #229

Merged
merged 1 commit into from
Jun 25, 2015

Conversation

JPrevost
Copy link
Member

This handles both non-responses and non-success responses when
attempting a Sword transfer.

closes #114

@richardrodgers
Copy link
Collaborator

Looks great: this is one we really needed to address, since I'm guessing this will be the most common hub failure. My only suggestion is to clean up the email template copy/paste stuff. The comment is from another template, and I think it should say 'deliver' rather than 'delivery'.

Thanks a lot, 👍

@JPrevost
Copy link
Member Author

Thanks. I'll fix that message and merge this morning.

This handles both non-responses and non-success responses when
attempting a Sword transfer.

closes #114
@JPrevost JPrevost force-pushed the 114_confirm_sword_package_accepted branch from 0b9c5be to 468319b Compare June 25, 2015 15:22
JPrevost added a commit that referenced this pull request Jun 25, 2015
…ccepted

Read response of attempted Sword
@JPrevost JPrevost merged commit 764d85d into master Jun 25, 2015
@JPrevost JPrevost deleted the 114_confirm_sword_package_accepted branch June 25, 2015 15:54
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Read response of swordTransfer
2 participants