On Apr 20, 4:14 pm, Andy Levy <andy.l..._at_gmail.com> wrote:
> On Tue, Apr 20, 2010 at 16:08, Nick Myers <nick..._at_gmail.com>
> Just curious here - as opposed to what? Whether people like or dislike
> VCSs, they're critical to good development practices. Whether you use
> Subversion or not, you need *something*.
The prior setup involved email, attachments, and a folder on the LAN.
Very messy. I guess I worded it poorly originally, but SVN is here to
stay, regardless. But we are curious what they do and don't like. We
shall see :-)
> You're describing Vendor Branches. Short version:
> 1) Keep a copy of the outside code in your repository
> 2) Copy it (within the repository) for your use
> 3) When you get an update from outside, update their code in your repository
> 4) Merge the changes into your customized copy
>
> Seehttp://svnbook.red-bean.com/nightly/en/svn.advanced.vendorbr.html
I have been reading this online book, but I guess this part didn't
click for me. I'll re-read and try to focus on this. So far the book
did a great job helping me setup everything and understanding basic
functionality.
Thanks,
Nick Myers
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2591597
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-04-21 15:03:21 CEST