On Thu, 10 Jan 2013 13:57:54 +0100
Stephan Beal wrote:
> On Thu, Jan 10, 2013 at 1:53 PM, Eduardo Morras wrote:
>
> > If he tries in shell 1
> >
> > fossil open repository
> > fossil server
> >
> > and in shell 2
> >
> > fossil clone http://localhost:8080/ copy.fossil
> >
> > should workaround
On Sat, Jan 12, 2013 at 9:58 AM, Eduardo Morras wrote:
> I thought that only in cgi mode it's forked for each request, I have to
> look that part of fossil code more deeply. I think in server mode fossil
> could/should/may keep running without exit after each request.
>
It's the other way aroun
This is with regards to the problem described here:
http://lists.fossil-scm.org:8080/pipermail/fossil-users/2008-February/60.html
We are seeing on the order of 3-5 of these a year in our heaviest hit
repos. While this may seem like no big deal the fact that it is so silent
is quite disruptive
On Sat, Jan 12, 2013 at 6:41 PM, Matt Welland wrote:
> This is with regards to the problem described here:
>
>
> http://lists.fossil-scm.org:8080/pipermail/fossil-users/2008-February/60.html
>
> We are seeing on the order of 3-5 of these a year in our heaviest hit
> repos. While this may seem
On Sat, Jan 12, 2013 at 7:31 PM, Richard Hipp wrote:
> Loss of situational awareness is a leading cause of airplane crashes and
> medical errors.
Here's another example of loss of situational awareness, which seems likely
to result in an adverse outcome:
http://chronicleoutdoors.com/wp-conten
on Jan 12, 2013, Richard Hipp wrote:
>
>
>On Sat, Jan 12, 2013 at 7:31 PM, Richard Hipp wrote:
>
>
>
>Loss of situational awareness is a leading cause of airplane crashes and
>medical
>errors.
>Here's another example of loss of situational awareness, which seems likely to
>result
>in an adver
On Sat, 12 Jan 2013 19:31:26 -0500
Richard Hipp wrote:
> I contend that this points up issues with your development process, not
> with Fossil. If your developers do not notice that a fork has occurred for
> days, then they are doing "heads down" programming. They are not
> maintaining situatio
On 01/12/2013 09:22 PM, John Found wrote:
If this is the case, I whould suggest better solution. Only 3..5 cases
in a year are not enough to train the team enough and to increase the
situation awareness of the people. Isn't it better to make fossil to
fork randomly with probability, let say, 1:
On Sat, 12 Jan 2013 21:22:28 -0800
"Michael L. Barrow" wrote:
>
> Please stop trolling
>
I am not trolling. It is "Reductio ad absurdum" that proves D. Richard Hipp is
wrong in his statement.
Solving technical problems by high-handed methods is wrong by definition.
--
John Found
http
On 01/12/2013 09:48 PM, John Found wrote:
I am not trolling. It is "Reductio ad absurdum" that proves D. Richard
Hipp is wrong in his statement. Solving technical problems by
high-handed methods is wrong by definition.
The source is available, so you should feel free to download and add in
t
On Sat, Jan 12, 2013 at 5:31 PM, Richard Hipp wrote:
>
>
> On Sat, Jan 12, 2013 at 6:41 PM, Matt Welland wrote:
>
>> This is with regards to the problem described here:
>>
>>
>> http://lists.fossil-scm.org:8080/pipermail/fossil-users/2008-February/60.html
>>
>> We are seeing on the order of
11 matches
Mail list logo
