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

Re: 1.9 issues

From: Stefan Sperling <stsp_at_elego.de>
Date: Fri, 24 Jan 2014 18:49:04 +0100

On Fri, Jan 24, 2014 at 09:20:35AM -0800, Ben Reser wrote:
> As we approach a 1.9 release (not sure what our time frame for release is but I
> think we were expecting roughly a year in Berlin last year) I think there are
> several issues that need to be discussed and final decisions made. I don't see
> any of this as a blocker to 1.9.0-alpha1, but they also provide us questions
> that we may want some help from our users in answering. This are the things
> that come to mind, I may have forgotten some so please add to the list if you
> have things.
> 1) svnauth vs svn auth: Right now it's a separate command. I believe this
> functionality is a client function. It really shouldn't be relegated to a
> separate program. Additionally, the separate command is one letter off from
> the svnauthz program that we already have. Since this is functionality that is
> entirely client specific and is intended to be used with the command line
> client, I'd argue we should move it into the client as a subcommand. This is
> going to take some work since svnauth has subcommands already.

My intention is to move into 'svn'. I have started this already but
got side-tracked and didn't get to finish it. I'll try to pick this up.

> 3) Merge tool UI from the conflict resolver. Trunk currently changes 'm' into
> running the external merge tool first if it exists. But this eliminates the
> ability to run the internal merge tool directly if you have an external tool
> configured. I vetoed the backport to 1.8.x, but I don't believe the UI
> concerns I raised have been settled.

That's because of my fix for issue #4426 (r1524145). I'd be fine
with reverting that change if no better solution can be found.
Received on 2014-01-24 18:51:20 CET

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.