I have posted just the code, which can be pasted in a file and be immediately useful in a project for anybody that would want the functionality.
But what if I would like to contribute to a capistrano? E.g. Mercurial support lacks :export copy option, which is really trivial to implement. Implementation is actually shorter (1 line) than current exception-raising version without :export (2 lines)... For rails there is quite a procedure to add something, including writing tests, getting reviews etc. What about capistrano? IMHO, the strategy wih local checkout and rsync to remote cached directory is the optimal strategy when remote server does not have access to the scm repository or when using distributed scm (e.g. git or mercurial) which are local by definition. What would constitute a good-enough proposal for inclusion of this strategy in capistrano? Or is this a non-starter because there will be no new strategy added to cap? Regards, izidor --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
