Todo List

Global svn_client_update4

Multiple Targets

• Up for debate: an update on multiple targets is *not* atomic. Right now, svn_client_update only takes one path. What's debatable is whether this should ever change. On the one hand, it's kind of losing to have the client application loop over targets and call svn_client_update() on each one; each call to update initializes a whole new repository session (network overhead, etc.) On the other hand, it's a very simple implementation, and allows for the possibility that different targets may come from different repositories.

Global svn_fs_copied_from

See how people like this, it can always be hidden behind the curtain if necessary.

Global svn_fs_file_contents

kff: I am worried about lifetime issues with this pool vs the trail created farther down the call stack. Trace this function to investigate...

Global svn_opt_print_generic_help2

Why is stream a stdio file instead of an svn stream?

Global svn_opt_subcommand_help3

Why does this only print to stdout, whereas svn_opt_print_generic_help() gives us a choice?

Class svn_wc_conflict_version_t

Consider making some or all of the info mandatory, to reduce complexity.