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

RE: Re: Delaying 1.3.0?

From: Flanakin Michael C Ctr HQ OSSG/OMR <Michael.Flanakin.Ctr_at_Gunter.Af.Mil>
Date: 2006-01-06 21:05:20 CET

What about removing the SSPI stuff for an RC2 release, but holding the final release until the issues are resolved? I agree that SSPI is a feature I'd be more than willing to wait for, but at least having some upgrade path would be nice, too.

Michael Flanakin
 

-----Original Message-----
From: Stefan Küng [mailto:tortoisesvn@gmail.com]
Sent: Friday, January 06, 2006 1:31 PM
To: dev@tortoisesvn.tigris.org
Subject: Re: Delaying 1.3.0?

Mark Phippard wrote:

> It doesn't sound like a bad idea. However, since you control the
> build of Neon, can't you just remove the #define HAVE_SSPI from the
> config.hw file for Neon?

I could of course do that. But the SSPI authentication is a big feature which I really would like to have included.

> Or even just build with Neon 0.24.7?

That's not really an option. Neon 0.25.x finally supports interrupted connections, which really is 'required'. Or don't you remember the log command fetching *all* the logs with <1.2 servers but still just showing the first 100 entries?

> Nothing is forcing you to use 0.25.4 or SSPI.

Sure, I'm not forced to use it, but I want to :)

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Jan 6 21:07:35 2006

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

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