Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
It is my understanding that although Mercurial has support from branches, the community generally clone repos instead of creating branches. Similar to the Darcs model, unlike the Git model.
I’m deploying a Ruby on Rails app with Capistrano and there I’d like to separate the production from the development branch. Should I point Capistrano to a different repo or should I use branches?
Has anyone used one model or the other of branching while dealing with Capistrano? Any problems with either?
yes mercurial supports several branching models cloning is probably the most common.
this certainly sounds like the ideal use of a named branch to me, but its ultimately a personal preference thing