I’m working on a change on my laptop. It’s not ready to be submitted to repository yet but I’d like to keep working on my desktop too. My change set is quite big and not only it contains modifications, it also contains new files and deleted files as well.
I could copy the complete local working copy to another machine and get the changes in place. However it sounds like a dirty solution (because I’m polluting metadata on another machine), and I’m transferring build artifacts unnecessarily too.
I tried transferring .patch files using TortoiseSVN but it keeps complaining about ‘patch belongs to an older revision’ (not true and why do you care?) or ‘lines do not match’ (yeah they don’t because i changed them). I didn’t like ‘continuous error popups’ experience at all.
I don’t want to install Cygwin, so command-line patch is out of question.
I guess the last option would be forking a new branch for this feature and go into a loop of ‘checkin/update’. However these are shown in trac history creating pollution there.
Any better ideas? Or anything I’m missing?
Branching is the clean solution. And has the additional advantage of giving you a backup while you’re working on this huge change. Not to mention, easy synchronization of future changes between machines.
But, you can probably get away with just zipping up the whole working directory and dumping it somewhere on the other machine.