allow persistent 1.1 & future persistents#9
Merged
pbrisbin merged 1 commit intopbrisbin:masterfrom Dec 31, 2012
gregwebs:master
Merged
allow persistent 1.1 & future persistents#9pbrisbin merged 1 commit intopbrisbin:masterfrom gregwebs:master
pbrisbin merged 1 commit intopbrisbin:masterfrom
gregwebs:master
Conversation
Owner
|
Isn't it dangerous to have no upper limit? |
Owner
|
Eh, I guess all we rely on is the |
pbrisbin
added a commit
that referenced
this pull request
Dec 31, 2012
allow persistent 1.1 & future persistents
Author
|
yep, exactly. We can always place an upper bound in the rare event that it breaks. |
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.
No description provided.