[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

svn client api comments

From: Martin Hauner <hauner_at_web.de>
Date: 2005-03-09 22:20:48 CET


i have a few comments about the svn client api. I'm looking on it from
the point of a svn (gui) client which likes to run some commands on
multiple files in one step and not on each single file.

svn_client_revert: takes multiple files.
svn_client_delete: takes multiple files.
svn_client_add(2): takes only a single input file.

Is there any reason why svn_client_add does take a const char* and
not a const apr_array_header_t* like revert and delete?

subcommanders c++ wrapper for add takes a list as input and calls
svn_client_add for each file. That's an easy workaround. But I think
the svn api would be a bit cleaner if add took a list too.

svn_copy: takes a single input file
svn_move(2): takes a single input file

It would be nice if those two took a list of files to copy/move as input.
If i move or copy source files in a working copy i typically want to move
a header and its source file together.

For the working copy case i can do the same as for add above, but in case
of copying or moving directly in the repository it wouldn't be a good idea.
Each single repository move or copy would request its own commit message...
and not just one message for the move/copy of all (selected) files.

what do you think?

Subcommander, http://subcommander.tigris.org
a x-platform Win32/Unix svn gui (qt) client & a text diff/merge tool.
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 9 22:24:43 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.