On Thu, Feb 16, 2017 at 9:56 AM <[email protected]> wrote: > Guess, I was wrong it's not in v1.0.3. >
No, it's enough a behavior change that it'll be a in a to-be-released v1.1. I'm suggesting that you could pip install the current commit in master as a workaround. I will vouch that it's thought to be stable: the only reason I've held off is to integrate some pull requests. -- You received this message because you are subscribed to the Google Groups "wal-e" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
