> The argument that cruft already exists in the commit log in jclouds/jclouds > should never justify > adding more cruft.
Touche ;-) In this specific case, I'm with you on introducing that as a new provider with a single commit. Not just for the reasons you mention, also because it helps make a clear distinction between "pre-core" and "in-core" time, and helps reinforce the idea that labs is a staging ground in a state of "churn" where history is not expected. Thanks for arguing your points, that really helped! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/563#issuecomment-58406169
