[LIBCLOUD-681] Allow for multiple record changes in one call#526
Closed
smstone wants to merge 1 commit intoapache:trunkfrom
Closed
[LIBCLOUD-681] Allow for multiple record changes in one call#526smstone wants to merge 1 commit intoapache:trunkfrom
smstone wants to merge 1 commit intoapache:trunkfrom
Conversation
Contributor
|
Thanks @smstone! This looks good to me, but could you please rebase and squash into a single commit? |
smstone
force-pushed
the
LIBCLOUD-681_multiple_record_changes
branch
from
ecac3db to
c5229a9
Compare
Author
|
@erjohnso I rebased and squashed, PTAL. Thanks. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue: https://issues.apache.org/jira/browse/LIBCLOUD-681