For those who wants to share their thoughts about an article I just posted : Does Capistrano need a copy_patches strategy?
http://philrathe.com/post/4286111528/does-capistrano-need-a-copy-patches-strategy On Mar 24, 3:50 pm, Philippe Rathe <[email protected]> wrote: > Hello, > > how one would do to prepare patches locally to be patched remotely > by the unix patch command? > > My SCM is git > > * Locally it would do a "git format-patch <since> <commit>" > The generated patches would be saved in /tmp > The since commit-ish would be known, it is the current release > commit-ish > * The patches would be sent to the remote > * The current release would be copied into the new release > * The patches would be applied in the new release > > And then I could just use > > cap deploy 0.2 > > Any idea about the best way to achieve it? -- * 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
