Re: [fossil-users] Enhancement: commit and close merged leaf

2013-07-11 Thread Jan Nijtmans
2013/7/10 Stephan Beal sgb...@googlemail.com: That well surpasses my understanding of how merging is tracked, so i'll just be quiet now ;). Well, merge-tracking is a part of fossil which I understand very well. So I did just a little bit hacking:

Re: [fossil-users] Enhancement: commit and close merged leaf

2013-07-11 Thread Harald Oehlmann
Am 11.07.2013 11:07, schrieb Jan Nijtmans: 2013/7/10 Stephan Beal sgb...@googlemail.com: That well surpasses my understanding of how merging is tracked, so i'll just be quiet now ;). Well, merge-tracking is a part of fossil which I understand very well. So I did just a little bit hacking:

Re: [fossil-users] Side-by-side diff improvement

2013-07-11 Thread Martin Gagnon
On Tue, Jul 09, 2013 at 06:46:48PM -0400, Richard Hipp wrote: On Fri, Jul 5, 2013 at 10:51 PM, Joel Bruick [1]j...@joelface.com wrote: Hi all, I've committed a pretty big changeto the diff code([2]http://www.fossil-scm.org/index.html/info/4081a91c84) , and I'd like

[fossil-users] Fossil Repository with remote users

2013-07-11 Thread Trachta, Nathan [USA]
Hi, I'm looking at using Fossil as a CM tool. Because of our systems I'm looking at having a stand-alone Fossil repository with remote users who need to have access to clones of the repository. This means the remote users will be sent a copy of the clone and have to send their updates. Is

Re: [fossil-users] Fossil Repository with remote users

2013-07-11 Thread Stephan Beal
On Thu, Jul 11, 2013 at 5:52 PM, Trachta, Nathan [USA] trachta_nat...@bah.com wrote: I’m looking at using Fossil as a CM tool. Because of our systems I’m looking at having a stand-alone Fossil repository with remote users who need to have access to clones of the repository. This means the

Re: [fossil-users] Fossil Repository with remote users

2013-07-11 Thread Stephan Beal
On Thu, Jul 11, 2013 at 5:57 PM, Stephan Beal sgb...@googlemail.com wrote: On Thu, Jul 11, 2013 at 5:52 PM, Trachta, Nathan [USA] trachta_nat...@bah.com wrote: I’m looking at using Fossil as a CM tool. Because of our systems I’m looking at having a stand-alone Fossil repository with remote

[fossil-users] Problem Importing From Git

2013-07-11 Thread Aaron W . Hsu
I have a Git fast-export that comes in at around 322MB in size or thereabouts. I am running the Windows version of Fossil from 2013-06. I run the following from within PowerShell and get some funny output: C:\... git fast-export --all | fossil import --git blah.fossil ]ad fast-import line:

Re: [fossil-users] Problem Importing From Git

2013-07-11 Thread Aaron W . Hsu
I should note that in the problem listed below, that this does not happen when I use the Linux version. -- Aaron W. Hsu | arcf...@sacrideo.us | http://www.sacrideo.us From: Aaron W.Hsu Sent: ‎Thursday‎, ‎July‎ ‎11‎, ‎2013 ‎6‎:‎24‎ ‎PM To: fossil-users@lists.fossil-scm.org I have a Git

Re: [fossil-users] Problem Importing From Git

2013-07-11 Thread Isaac Jurado
El 12/07/2013 00:28, Aaron W.Hsu arcf...@sacrideo.us escribió: I have a Git fast-export that comes in at around 322MB in size or thereabouts. I am running the Windows version of Fossil from 2013-06. I run the following from within PowerShell and get some funny output: C:\... git fast-export

Re: [fossil-users] Fossil Repository with remote users

2013-07-11 Thread Isaac Jurado
El 11/07/2013 17:52, Trachta, Nathan [USA] trachta_nat...@bah.com escribió: Hi, I’m looking at using Fossil as a CM tool. Because of our systems I’m looking at having a stand-alone Fossil repository with remote users who need to have access to clones of the repository. This means the

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.