| commit | 2a2a817024e0a19b7c7f700dc05c8e6af22e33c9 | [log] [tgz] |
|---|---|---|
| author | Christopher Tate <ctate@google.com> | Mon May 01 16:11:48 2017 -0700 |
| committer | Christopher Tate <ctate@google.com> | Mon May 01 16:59:16 2017 -0700 |
| tree | 989422c55f0657ff5b8eca9072f8b0a0d842e679 | |
| parent | f8e7cbffb9de3f16d1ee4329190a0423c2319545 [diff] |
Don't mix "current dataset" tokens for different backup transports Previously, one could poison the current-dataset tracking by inopportunely-timed use of the local (aka development) transport. Now you can't: we reset the 'current dataset token?' tracking whenever the user changes the active transport. Also don't double-allocate return values sometimes. Bug 37694618 Test: manual Change-Id: I2cf5d42774522af830aecb99e65f43c4d0b5ce76