[Dev] commit() and refresh()

[Andi Vajda]

I just added a new method to RepositoryView called refresh().
That method refreshes the view it is called on with all the changes that were 
committed in other views since the last time refresh() or commit() was called 
on that view. This method also sends the usual history change notifications 
gotten through commit() until now.

RepositoryView.commit() now calls RepositoryView.refresh() before actually 
committing all the changes made in the view it is called on.
Therefore the history change notifications are now sent in two batches, first 
during refresh for changes that occurred in other views, then after commit 
succeeds, the changes that were committed.

Therefore, when you're only interested in changes that happened in other views 
and are not yet ready to commit the changes in your own view, you should now 
be calling refresh() instead of commit().

Andi..