@musicman Yes, I think #git is overly complicated for most projects' needs, but it has mindshare, so people often demand it when another VCS would be more appropriate. It'd be great if transitioning from one to another was a well-understood problem, but it isn't.
Is that #Emacs that is trying to move from #svn to git with #ESR's help and having a difficult time of it?
How many of you *don't* enjoy using #git or #mercurial or #svn or any kind of source control at all? I want to find people who just don't like it and wish there was a better way. I know you're out there!
For reasons I need to work for one project on a svn checkout that's a samba share. However I get this error:
$ svn update svn: E200033: Another process is blocking the working copy database, or the underlying filesystem does not support file locking; if the working copy is on a network filesystem, make sure file locking has been enabled on the file server svn: E200033: sqlite[S5]: database is locked svn: E200042: Additional errors: svn: E200033: sqlite[S5]: database is locked
Do you know which locking setting is the right one?
@musicman I normally only use #git when I have no other choice. Its commands seem obtuse when compared with mercurial ( #hg ) and #fossil ( which is still my favorite dvcs [ and favorite vcs in general, as I never used #cvs or #svn ] ). I have to look up everything I want to do with it.
If #git isn't the right version-control system for your work, there are others that may or may not fit your needs. Look at #hg (mercurial), #bzr (bazaar), #fossil, #darcs, or #svn (subversion). I know svn has a gui tool available for Windows. Not sure what kind of gui tools the others may offer.