Lieven Govaerts wrote:
> Open ends:
> 1. There is no way now to give the user a clear log of what has
> happened. svn_client_delete3 only receives info on the last commit, so
> it only prints that revision number.
> I'd like to have it print something like this:
> $ svn rm http://srv/repos1/A http://srv/repos1/B http://srv/repos2/X
> D http://srv/repos1/A
> D http://srv/repos1/B
> Committed revision 2.
> D http://srv/repos2/X
> Committed revision 5.
> I didn't look into it more deeply, so that might be easy to do or not.
> Suggestions are welcome.
I'd prefer to see clearer groupings (with headers). Also, we use full words
for commit actions.
$ svn rm http://srv/repos1/A http://srv/repos1/B http://srv/repos2/X
Committed revision 2.
Committed revision 5.
> 2. The issue report talks about using the UUID to match paths with
> repositories, but I fail to see the reason why that would be needed. Is
> there anything wrong with my naive path-based implementation?
I prefer URL-based comparisons because it seems to me more likely that
someone will have somehow naively wound up with multiple repositories that
have the same UUID (via dump/load, or 'cp -a' of some template repository,
or...) than that they have multiple repositories at the same path. :-)
C. Michael Pilato <email@example.com>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on Tue May 29 17:16:34 2007