On 6/04/2013 5:48am, Bill Freeman wrote:
Just to be clear, are you saying that svn lets you do check ins on a private branch when you are not connected to the network (and thus can't access the central repository)?
No. I said ...
That is true if the SVN repo is on the network. But there are a number of ways to organise things with a local repo if that is your situation. However, if that is your situation, I agree git or hg would be better.
When offline with svn the only way to commit changes is to a local svn repo. Then you would need to export your local changes over the top of the checked-out code from the networked repo and commit when you get a network again. You wouldn't do that though. You would abandon svn for git or hg or similar.
On Thu, Apr 4, 2013 at 7:30 PM, Mike Dewhirst <mi...@dewhirst.com.au <mailto:mi...@dewhirst.com.au>> wrote: On 5/04/2013 12:36am, Bill Freeman wrote: It is also possible to use a non-distribted VCS, like Subversion, but you lose, IIUC, the ability to check in incremental stuff If you work in (say) your own branch of a SVN repo you can check in as often as you like. And you can merge other branches - including trunk - into your own as often as you like. That is the "way" it is intended to be used. Only when you are convinced all the merged changes (including trunk) in your own branch work properly would you be confident in merging back into trunk. So if "the network is the computer", SVN *is* distributed and increment-friendly. I think git and friends are very popular because so many devs like to operate with laptops in cafes and trains etc. or check what was their in an older version, when not connected. That is true if the SVN repo is on the network. But there are a number of ways to organise things with a local repo if that is your situation. However, if that is your situation, I agree git or hg would be better. I'm just planning a deployment scenario with SVN: dev --> staging (sharing the dev database) --> production. I'll open up a deploy branch in the repo and merge trunk into that when I'm ready to deploy. Then I only need a script on the production server to fetch the deploy branch whenever I want to update production. Mike -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@__googlegroups.com <mailto:django-users%2bunsubscr...@googlegroups.com>. To post to this group, send email to django-users@googlegroups.com <mailto:django-users@googlegroups.com>. Visit this group at http://groups.google.com/__group/django-users?hl=en <http://groups.google.com/group/django-users?hl=en>. For more options, visit https://groups.google.com/__groups/opt_out <https://groups.google.com/groups/opt_out>. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
-- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
