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

Re: svn commit: rev 7571 - branches/partial-authz-dev

From: Greg Stein <gstein_at_lyra.org>
Date: 2003-10-31 00:46:21 CET

On Thu, Oct 30, 2003 at 03:16:16PM -0600, kfogel@tigris.org wrote:
> Author: kfogel
> Date: Thu Oct 30 15:16:15 2003
> New Revision: 7571
> Added:
> branches/partial-authz-dev/
> - copied from rev 7570, trunk/
> Log:
> Branch for development of new partial authorization code. See this
> thread

What are the development steps here? Before doing a branch, I'd think
there were quite a few low-hanging fruit that could be completed first.

Off-hand, I'd say the editor change is one, and then propagate those
changes throughout the editors in the code. Next would be to remove much
of the "Neon shim" code in ra_dav. Then, maybe this authz work, and then
finally tying it together.

I also seem to recall a phone conversation where we might need to
differentiate between a plain checkout and an update? Or did that get

Also, in the branch, you've now added a couple new editor callbacks rather
than adding an "incomplete" flag to the close_dir. Where'd that come up?

I think part of the point here is that the direction you're going with
this is very unclear. And given an unknown on overall direction, it is
further unclear on whether to provide feedback on the branch. What are the
specific goals [of the branch] at this time that we should compare your
development against?


Greg Stein, http://www.lyra.org/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 31 00:47:20 2003

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.