[Psi-devel] Subversion repository

[Remko Troncon]

> that darcs has?  (I know darcs has the thing where it shows you each  
> patch one by one and the explanation associated with it ... i really  
> like that as I've always wished subversion would auto-show you change  
> logs upon update) 

That's indeed one of the problems, but not really crucial i suppose
(you can request the difference between the local wc and the repo before
updating)

One of the things that I miss a lot is the disconnected (local) commits.
This is probably something that Subversion will never have, because of its 
repository-centric nature. One way to overcome this is to add a script
'darcsify' to our source tree that creates a darcs tree of your local 
checked out SVN working copy, and you can start incrementally recording
your new giant patch, and then in the end committing it all to Subversion.

However, the thing i miss the most is that, upon committing, you cannot review
and select the local changes you want to commit and the ones you do not want to
commit. This is not only interesting to ensure you are not committing debug
info etc., but also allows to do 'quick fixes' in your current working copy and
committing them. This is not a fundamental Subversion issue, and is probably
easily implementable in the svn client, but the SVN people don't seem to
understand why this is interesting. I have written a Python script that allows 
you to review and select your changes, only commits the ones you selected, and
leaves the other changes in the working copy. However, i'm not totally
satisfied with it. I would like a tighter binding with Subversion than just the
command-line 'svn' options to feel completely safe with my script, so I should 
either look into the Python SVN bindings, or just program a '--interactive' 
flag for 'svn' myself.

cheers,
Remko