On Nov 4, 2004, at 3:51 PM, Geir Magnusson Jr wrote:
On Nov 4, 2004, at 3:45 PM, Dain Sundstrom wrote:
It is covered in the subversion book http://svnbook.red-bean.com/
Can understand why you would want to branch for security, but I think
you should keep working on your deployment stuff in the
On Nov 4, 2004, at 4:09 PM, Dain Sundstrom wrote:
On Nov 4, 2004, at 3:51 PM, Geir Magnusson Jr wrote:
On Nov 4, 2004, at 3:45 PM, Dain Sundstrom wrote:
It is covered in the subversion book http://svnbook.red-bean.com/
Can understand why you would want to branch for security, but I
think you
Sorry, I thought there was a follow option guess I was wrong.
-dain
On Nov 4, 2004, at 5:32 PM, Aaron Mulder wrote:
I like to think that I'm not an idiot (though I am getting a
littly grumpy, for which I apologize). I reread the entire branching
chapter in the Subversion book, and it looks
On Thu, Nov 04, 2004 at 08:32:47PM -0500, Aaron Mulder wrote:
So, I ask again, without any more RTFMs, is there any convenient
way to branch in such a way that all the unmodified files stay in lockstep
with the trunk, and only the modified files are tracked differently?
No, there is
On Nov 4, 2004, at 3:45 PM, Dain Sundstrom wrote:
It is covered in the subversion book http://svnbook.red-bean.com/
Can understand why you would want to branch for security, but I think
you should keep working on your deployment stuff in the main trunk.
If it's easy to fold back in, why not do in
