Capistrano v2.5.13 ruby 1.8.7 mercurial scm bitbucket repo I was impatient with the clone stage of my deploys, so I hacked in a deploy strategy to do the following:
1. clone the current release (if previously deployed) on the target instead of cloning from the remote repo 2. pull from the remote repo (only get what changed) 3. update to the requested revision Is there any interest in making this type of strategy available in cap? Perhaps there are some flaws in this approach that I'm unaware of; otherwise, I'd be happy to contribute. Thanks, Dave -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
