On Mon, 16 Jul 2007, Mark Phippard wrote:
> On 7/16/07, Daniel Rall <dlr@collab.net> wrote:
...
> >The remaining loose ends for 1.5.0 still need to be enumerated, and
> >tossed into the issue tracker (even if only at a very coarse
> >granularity). Here's a starting point -- just a strawman -- for the
> >list of remaining loose ends:
> >
> >- 1.4.x/1.5 client/server incompatibilities. (Reported by glasser in
> > <1ea387f60707042016n2e7ae3fxb9f5cd2b078a50d5@mail.gmail.com>.)
> >- Sparse directories/--depth option
> > - See the "Current Status" section of notes/sparse-directories.txt.
> > - Review "TODO(sd)" comments in the code.
> >- ra_serf/ra_neon
> > - Progress callback busted between May 16 and June 21. (Reported by
> > Dan C. from Google in
> > <e6b000d70707091119o11097f50o8e04518499fd151d@mail.gmail.com>.)
> > - Outstanding SVN DAV library config issues?
> >- ra_serf-specific
> > - Remaining abort()'s?
> > - (What else...?)
> >- XFailing tests
> > - (Which in particular absolutely need to be resolved...?)
> >- Changes needed by Subclipse...?
> >- Changes needed by TortoiseSVN...?
> >- Language bindings updates for API changes...?
>
> - fsfs transaction name problem
> - DAV write-through proxy feature. Someone posted a question on
> users@ without a reply:
> http://svn.haxx.se/users/archive-2007-07/0100.shtml
> I still wonder if it could be made to work cleaner, such as use
> svnsync without any hooks.
> - svnmerge conversion script? I think this has been talked about but
> I do not know who plans to do it.
DannyB had some Python code to do this at one point.
- Utility to mark revisions as merged for a branch
- Necessary to leverage Merge Tracking's "merge outstanding revs
from branch" functionality.
- Should be easily callable against all branches in a repos, and
handle marking the revs for batches of branches as merged.
- Integration with cvs2svn a plus for doing this during a migration
from CVS -> Subversion.
- application/pgp-signature attachment: stored
Received on Tue Jul 17 02:52:19 2007