Re: [fossil-users] SSH client updates.

2013-07-12 Thread Stephan Beal
On Fri, Jul 12, 2013 at 3:15 AM, Matt Welland estifo...@gmail.com wrote: My vote is to go with the new behaviour only. More options usually means more pain - albeit after getting though any transition troubles. +1 -- - stephan beal http://wanderinghorse.net/home/stephan/

Re: [fossil-users] SSH client updates.

2013-07-12 Thread Rene
On 2013-07-12 01:49, Andy Bradford wrote: Thus said Rene on Thu, 11 Jul 2013 22:31:48 +0200: I would prefer to not have that option. test-http is for testing a new transport method. If you give someone read acces to your ssh repo then test-http circumvents that. In fact test-htp makes you

Re: [fossil-users] SSH client updates.

2013-07-11 Thread Andy Bradford
Thus said Rene on Thu, 11 Jul 2013 22:31:48 +0200: I would prefer to not have that option. test-http is for testing a new transport method. If you give someone read acces to your ssh repo then test-http circumvents that. In fact test-htp makes you while connected setup user I agree with you

Re: [fossil-users] SSH client updates.

2013-07-11 Thread Matt Welland
My vote is to go with the new behaviour only. More options usually means more pain - albeit after getting though any transition troubles. I am biased in this. The old method seemed brittle. However I haven't yet tested your new code. Hopefully I'll get a chance to do that next week some time.

[fossil-users] SSH client updates.

2013-07-10 Thread Andy Bradford
Folks, As I mentioned before, I've been attempting some modifications to the fossil SSH URL handling. I'm at a point where I could use some feedback regarding the previous method for handling SSH. Originally, fossil would fork an SSH connection and then communicate with the remote shell

Re: [fossil-users] SSH client updates.

2013-07-10 Thread Stephan Beal
On Wed, Jul 10, 2013 at 9:51 AM, Andy Bradford amb-fos...@bradfords.orgwrote: ... Is there value in keeping this old method? I personally don't see any, but then I don't have the background to know why it was done this way. If i'm not sorely mistaken, the current approach was done

Re: [fossil-users] SSH client updates.

2013-07-10 Thread Martin Gagnon
On Wed, Jul 10, 2013 at 01:51:05AM -0600, Andy Bradford wrote: Folks, As I mentioned before, I've been attempting some modifications to the fossil SSH URL handling. I'm at a point where I could use some feedback regarding the previous method for handling SSH. [snip] I like the idea

Re: [fossil-users] SSH client updates.

2013-07-10 Thread Rene
On 2013-07-10 21:31, Martin Gagnon wrote: On Wed, Jul 10, 2013 at 01:51:05AM -0600, Andy Bradford wrote: Folks, As I mentioned before, I've been attempting some modifications to the fossil SSH URL handling. I'm at a point where I could use some feedback regarding the previous method for

Re: [fossil-users] SSH client updates.

2013-07-10 Thread Martin Gagnon
On Wed, Jul 10, 2013 at 10:32:26PM +0200, Rene wrote: On 2013-07-10 21:31, Martin Gagnon wrote: On Wed, Jul 10, 2013 at 01:51:05AM -0600, Andy Bradford wrote: Folks, As I mentioned before, I've been attempting some modifications to the fossil SSH URL handling. I'm at a point where I

Re: [fossil-users] SSH client updates.

2013-07-10 Thread Martin Gagnon
On Wed, Jul 10, 2013 at 05:24:29PM -0400, Martin Gagnon wrote: On Wed, Jul 10, 2013 at 10:32:26PM +0200, Rene wrote: On 2013-07-10 21:31, Martin Gagnon wrote: On Wed, Jul 10, 2013 at 01:51:05AM -0600, Andy Bradford wrote: Folks, As I mentioned before, I've been attempting some

Re: [fossil-users] SSH client updates.

2013-07-10 Thread Andy Bradford
Thus said Martin Gagnon on Wed, 10 Jul 2013 17:50:40 -0400: Sorry, *my* mistake.. I didn't notice the new version of the patch on latest Andy Bradford email. My test was made with the previous patch. Not a problem. I should probably setup a fossil clone that can be accessed, rather

Re: [fossil-users] SSH client updates.

2013-07-10 Thread Andy Bradford
Thus said Martin Gagnon on Wed, 10 Jul 2013 17:50:40 -0400: Work fine now.. sorry for the noise.. Speaking of noise, time to add a little more (because my original email wasn't quite long enough). The new options that I've added are not yet fully documented in the usage/help (not having