Svn: local commits

Question

Subversion: is it possible to make local revisions without clicking them and push them to a later date - or is this a drawback of this function, why is it called "centralized"?

Answer 1

Unable to execute local commits with Subversion.

This is because, as a centralized version control system, your local working copy does not have all the information that the server has about past versions, logs, etc. that it would have if it were a distributed version control system ( GNCR).

A working copy of the disruptive operation contains a copy of all files as they are extracted so that you can undo the modified files without accessing the server.

If you really want to do local commits, you should take a look at SVK , which is built on top of Subversion and provides DVCS as functions.

Answer 2

A significant part of the above is somewhat outdated, and since this question appears as a result of a google search for "svn local commit" here:

Consider using the git-svn package (along with git-gui if you don't know git) to make local commits possible and easy, with full remote SVN integration. A good review / tutorial / use case is here . I just started using this process with Sourceforge projects, so I can’t report any problems yet. Be sure to get the authors file correctly!

EDIT: Updated link. Thank hdl

Answer 3

You can have the SVN interface connected to GIT or Mercurial Bridge. Since GIT and Mercurial can execute local commits, you can use them like this. Maybe check git-svn or something similar (I remember that there was a bazaar-svn, but not sure).

Answer 4

That is why it is called centralized. You can try using repo inside repo. One of them is local, and the other is remote. Then you transfer the entire internal repository to the remote.

Answer 5

As others have said, no.

I would highly recommend try to use anything remotely janky with svn.

I did not use SVK enough to recommend against it, it seemed good enough. However, I am skeptical about using anything built on top of SVN for the whole project without any hacks. I use SVN enough to know that even normal duty cycles can set it on fire if you are not careful.

We use SVN at work. I use bzr and bzr-svn to do all my interaction and it works wonderfully . My workflow is similar:

$ bzr branch file:///var/svn/project ~/project

(hack, hack, hack)

$ bzr commit -m "commit log" (Repeat)

when i'm ready

$ bzr push

Yes, instead of updating you have $ bzr merge and committing changes (maybe putting off what you are working on), but local commits are a very good thing, and racks too (racks are like returning with saving)

I think git is handling this. I heard that this is not as complete as bzr-svn, but I cannot confirm this.

But using DVCS with svn repository is a good way!

Answer 6

In addition to BobC's answer, for mercurial you should use hgsubversion .

Answer 7

No! git however can do this, and you can use git-svn to synchronize with the original repository.

Answer 8

To get the best of both worlds, SVK was built on top of Subversion, but maintained local state, so you can do local commits ...