Personally I think it depends on what we are promoting. In this case I don't see much value in preserving the history, unless some contributor wants to. We say the main repo holds the production ready code, so it could be OK to have only one commit for swift if it is the first commit to be considered production ready.
Other providers such as chef might be different. It has been stable for ages, and also noorul, who contributed some patches, expressed to me the interest in keeping the commit history. Contributors like seeing their names in the history (I like that), and we should preserve that if they express so. So in the end I think it is a matter of the maturity of a provider, how it is being used and how people is contributing to it. I don't know in detail the swift history, but I'd be OK both approaches. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/563#issuecomment-58390391
