[ACCEPTED]-Working offline with SVN on local machine temporary-offline
Your problem sounds to me like the use case 2 for
- set up your Git repo:
git svn clone http://svn.example.com/project/trunk
- while being online, commit your changes to SVN
- before going offline, do a
git svn rebaseto get your Git repo in sync with the SVN repo
- while being offline, commit to the Git repo using
- when getting back online again, do a
git svn dcommitto push your changes back to the SVN repo
I'm using this workflow daily!
You 1 get two huge advantages doing so:
- your complete SVN history is backed up in the Git repo and in every Git repo that gets cloned from that one
- while being offline, you can view the commit messages, checkout other branches, etc.
Ridiculous answer would be to migrate to 12 another versioning tool, no offence!
I had 11 the exact issue.
Been using SVN on my "real" server 10 where the "real" repository is.
When I went 9 out with my laptop, without internet I would 8 simply duplicate the "real" repository on 7 this laptop (VisualSVN + TortoiseSVN), work 6 on it, change/commit whatever, and when 5 come back simply "sync" the new 'revision' files 4 to the "real" repository.
To be a bit more 3 clear: Have two SVN servers, one locally 2 on your laptop (the clone) and one on your "real" server 1 (obviously). Just sync between the two.
You can access svn repositories with mercurial.
I've been using git on a project that uses 11 SVN for the same reason you describe above. There 10 is some getting used to git/mercurial but 9 after a while I really like the new approach. Further 8 I never had any issues with using git-svn, never 7 have tried mercurial and svn..
If you are 6 onto Mercurial and are still looking for 5 a good tutorial with one or two chuckles 4 in between check out this tutorial written by Joel 3 Spolsky. And as mentioned before, surely 2 is a great opportunity to get started with 1 DVCS.
Disclaimer: I'm the author of SOS (SVN Offline 13 Support).
I wrote this easy to use command-line 12 tool to solve exactly the problem of working 11 with SVN offline, but it works not only 10 within SVN checkouts, but for any VCS working 9 copy (e.g. Bazaar, Git, fossil), or even 8 in untracked file trees. SOS allows simple 7 commits, branching, switch/update operations, without 6 all the complex semantic background knowledge 5 required by traditional VCS. After coming 4 back online, you can integrate all changes 3 back to your underlying VCS.
Installation 2 requires a Python 3, and is handled via 1
pip install -U sos-vcs
There's always SVK as well. I haven't used 2 it in years though, so I'm not sure of how 1 well it works anymore.
More Related questions