Carroll, Andrew wrote:
>
> At our work we currently use SVN to manage our projects and files. We
> do this by the checkout, modify and commit cycle or whatever you want
> to call it. Problem is, once I check it out, I have no way (other
> than making folders) to track my changes to the working copy. I want
> to track my local changes using SVN and then somehow get them from a
> local SVN to the work SVN. I normally start out by checking out a
> working copy to my local area. I want that checkout to go into my
> local SVN and then check out from my local SVN so I can track my own
> changes.
>
>
>
> I don't however know what process is involved in getting the local SVN
> up to the work SVN. What is that process called?
>
>
>
> If this question has been posted before then just tell me to go read
> the history of this list (maybe you could give me some search terms
> though). Thanks.
>
>
>
>
>
> Andrew Carroll
>
> Software Services
>
> 405-744-4943
>
> andrew.carroll@okstate.edu
>
>
>
I think the typical scenario is to use a private branch on the
repository to store your working changes and then merge from that to the
trunk. This has multiple advantages - 1) if you go stepping out in
front of a bus (I've seen college campus bus drivers), your mostly up to
date work can be picked up by another developer, 2) when your windoze
box crashes your work is not lost and can be picked up from any other
machine, 3) cheap copies on the repository make storage easier on everyone.
This way, you make a change to a file, commit that change to your
branch, run a test on your local machine to verify fix, and repeat that
process until you have a total fix. Lather, rinse, repeat.
Regards,
Frank
Received on Wed Oct 11 17:09:08 2006