Comments on Code Codex: Subversion is the most important tool that a CS st...

Hi,i am getting below the error.Berkeley DB error ...

2009-03-18T03:42:00.000-07:00

Hi,

i am getting below the error.

Berkeley DB error for filesystem E:/SubversionRepository/db while opening 'nodes' table:No such file or directory.

How to fix this.please help me.

Thanks,
Velmurugan.

By the way, I'd like to add one more comment wrt. ...

2008-05-04T03:13:00.000-07:00

By the way, I'd like to add one more comment wrt. branching.

To use branches (so called topic branches) to develop new features, test ideas etc. you rather need private branches. Minimally, you would need to be able to freely create and delete branches, without worrying about unique names. Best, those private branches with work in progress should be kept private, and not visible / published (this for example allow to rewrite history e.g. using rebase / transplant / cherry-picking to arrive at perfect patch series, clean history[1]).

And this in my opinion requires distributed version control system such as git, Mercurial or Bazaar.

[1] Like in those science assignments, where not only final result matters, but also a way you arrived at the result.

Jakub- You're right about the title. I went back...

2008-05-03T17:52:00.000-07:00

Jakub- You're right about the title. I went back and forth many times on it, and ended up using Subversion as it sounded catching. Good points about other uses of versioning.

CVS is hardly the grandaddy. RCS is older, and act...

2008-05-02T18:18:00.000-07:00

CVS is hardly the grandaddy. RCS is older, and actually still used in a number of places (think federal government).

RCS track single files, and not state of project as a whole, and it uses lock-edit cycle instead of edit-merge.

CVS is hardly the grandaddy. RCS is older, and ac...

2008-05-02T16:22:00.000-07:00

CVS is hardly the grandaddy. RCS is older, and actually still used in a number of places (think federal government).

I'd rather the title of this blog entry was "Versi...

2008-05-02T07:34:00.000-07:00

I'd rather the title of this blog entry was "Version control is the most important tool..." (or "revision control", etc.), not "Subversion...", as it is not about Subversion but most about version control system.

There are two important issues that version control systems help with that you haven't mention (well, one was mentioned), perhaps because of lack of good support for it in Subversion:

* branching which allow to test different ideas without affecting main development, and allow to do maintenance of stable version while developing new features. Subversion needs third-party support (svnmerge, SVK) to make merging easy, and easy branching without easy merging is not conductive.

* bisect (or diff debugging) which allow to find where bug is by finding which commit introduced the bug. As far as I know Subversion doesn't have direct support for that, although it is possible that one of main contributors to Subversion invented term diff debugging