Re: [fossil-users] Fossil crashing when opening or checking out a repository.

Trying to open the same repository under a Linux system (fossil version 1.33 [5b456cfa6b]) gives me this: "[1]9388 segmentation fault fossil open /path/to/Joystick.fossil" On 15 April 2016 at 11:31, Michael Richter wrote: > Platform: Windows 10. > Fossil version: 1.34

[fossil-users] Fossil crashing when opening or checking out a repository.

Platform: Windows 10. Fossil version: 1.34 [62dcb00e68] After making a few changes to a project (IAR Embedded Workbench for ARM) and committing them on a feature branch, I tried to check out the main development branch. The result was a hard crash. My repository is now in a state where I can't

Re: [fossil-users] How to actually >use< TH1?

Thus said Johan Kuuse on Wed, 13 Apr 2016 06:52:30 +0200: > But I have had no success when trying to use TH1 with the xfer pages. > What I try to achieve is to use a TH1 script to check the contents of > a commit message, and conditionally reject the commit depending on the > message syntax.

Re: [fossil-users] CGI arguments other than "repository" and "notfound"

On 4/14/16, Thomas Levine <_...@thomaslevine.com> wrote: > Hi, > > "fossil serve" provides several options that I can't find for > the CGI program "fossil cgi". See the source code (https://www.fossil-scm.org/fossil/artifact/2c2d97aec0?ln=2055-2190) for a complete list. Undocumented options

[fossil-users] CGI arguments other than "repository" and "notfound"

Hi, "fossil serve" provides several options that I can't find for the CGI program "fossil cgi". The only "cgi" options I have managed to find are "repository" and "notfound", as documented here. https://www.fossil-scm.org/index.html/doc/trunk/www/server.wiki I want to use --repolist and

Re: [fossil-users] HOWTO: TLS-protected Fossil with nginx and Let's Encrypt

On Apr 14, 2016, at 3:50 PM, Joerg Sonnenberger wrote: > > On Thu, Apr 14, 2016 at 03:32:48PM -0600, Warren Young wrote: >> STEP 1: Split your “server” configurations > > I don't think this is necessary at all. It is. We want the proxy server to redirect all

Re: [fossil-users] HOWTO: TLS-protected Fossil with nginx and Let's Encrypt

On Thu, Apr 14, 2016 at 03:32:48PM -0600, Warren Young wrote: > STEP 1: Split your “server” configurations I don't think this is necessary at all. > STEP 2: Prepare for the Let’s Encrypt challenge/response sequence This part can just statically go into the same server block, no need for a

[fossil-users] HOWTO: TLS-protected Fossil with nginx and Let's Encrypt

The existing documentation [1] for setting up SSL with Fossil is pretty thin. “Just set up an SSL web proxy,” it says. Yeah, “just.” :) Other advice recently given on this list is to use stunnel, but that’s only of use when Fossil hosts the whole web site, so you just need to proxy Fossil.

Re: [fossil-users] feature implemented or suggestion for stash

On 4/14/2016 11:10 AM, Stephan Beal wrote: On Thu, Apr 14, 2016 at 7:00 PM, Warren Young > wrote: On Apr 12, 2016, at 11:30 PM, Stephan Beal > wrote: > i haven't ever bisected. Wow…

Re: [fossil-users] feature implemented or suggestion for stash

On Thu, Apr 14, 2016 at 7:00 PM, Warren Young wrote: > On Apr 12, 2016, at 11:30 PM, Stephan Beal wrote: > > > > i haven't ever bisected. > > Wow… > > I don’t bisect every day, but when I do bisect, I bisect with Fossil. :) > i've just been lucky -

Re: [fossil-users] feature implemented or suggestion for stash

On 4/14/16, Warren Young wrote: > > I suppose if you’re working on software with 100% regression test coverage, > such problems would never become buried in the project history: as soon as a > change breaks things, you get told about it by the test harness. Not so. The better

Re: [fossil-users] feature implemented or suggestion for stash

On Apr 12, 2016, at 11:30 PM, Stephan Beal wrote: > > i haven't ever bisected. Wow… I don’t bisect every day, but when I do bisect, I bisect with Fossil. :) Bisecting is most useful when you get a bug report from the field and can’t see from that report how any of the