On 17 Oct 2013, at 18:40, Richard Hipp wrote:
> On Thu, Oct 17, 2013 at 1:21 PM, Stephan Beal wrote:
> On Thu, Oct 17, 2013 at 7:17 PM, Richard Hipp wrote:
> Currently, Fossil requires REQUEST_URI and SCRIPT_NAME at a minimum, and will
> construct PATH_INFO from those two if it is missing. I
Hello,
I've just tried upgrading from fossil 1.25 to fossil 1.27 on my server, which
uses Jetty as the CGI server.
I just see an error:
Bad Request: missing REQUEST_URI
and of course, Jetty isn't sending a REQUEST_URI. This environment variable
isn't part of the CGI 1.1 spec, so I suppose
On 13 Dec 2011, at 16:56, Richard Hipp wrote:
> On Tue, Dec 13, 2011 at 11:52 AM, Chad Perrin wrote:
>
>> Point of curiosity: Is there a Twitter feed for Fossil?
>
> I was thinking the other day that it might be cool to have a feature whereby
> a Fossil server would tweet every time it got a
On 25 Nov 2011, at 22:02, Barry Kauler wrote:
> Hi guys,
> I am just getting started with Fossil again, after a brief fling back
> in late 2009. I was very impressed, but my project has lots of
> symlinks, which is what brought me to a halt before.
>
> When I created my "woof2" repository, I tic
On 22 Nov 2011, at 22:10, Garth Dahlstrom wrote:
> Hi all,
>
> Short Question: Can anyone build a "mostly static" fossil executable
> on Solaris 8 or 9 and post it somewhere?
>
> Longer Explanation:
> The only Solaris box that I have capable of building anything is a
> Solaris 10 box; there ar
On 21 Nov 2011, at 01:13, Richard Hipp wrote:
>
> On Sun, Nov 20, 2011 at 7:56 PM, Chris Peachment wrote:
>> I'm using fossil version 1.20 on Linux for both server and client
>> computers.
>>
>> I want to use fossil command line instructions to initialise an
>> empty repository. I use:
>>
>>
On 3 Oct 2011, at 17:37, Lluís Batlle i Rossell wrote:
> On Mon, Oct 03, 2011 at 05:13:35PM +0100, Ben Summers wrote:
>>
>> On 3 Oct 2011, at 16:20, Lluís Batlle i Rossell wrote:
>>> I think that's exactly what I want. Anyone against?
>>
>> Might be be
On 3 Oct 2011, at 16:20, Lluís Batlle i Rossell wrote:
> On Mon, Oct 03, 2011 at 05:05:13PM +0200, Stephan Beal wrote:
>> 2011/10/3 Lluís Batlle i Rossell
>>
>>> What would happen if JSON answers had not 'no-store'? Would not be
>>> 'no-cache'
>>> enough? It should be up to the json clients tho
On 15 Sep 2011, at 00:17, Stephan Beal wrote:
>
> As Richard mentioned earlier, the current fossil login mechanism does not
> tolerate a given user being logged in multiple times (each new login
> invalidates the previous one). While this almost certainly isn't a real
> limitation for the HTML
On 14 Sep 2011, at 21:36, Richard Hipp wrote:
>
>
> On Wed, Sep 14, 2011 at 4:30 PM, Joshua Paine wrote:
> On 9/14/2011 4:22 PM, Ben Summers wrote:
>>> HTTP basic authentication is widely supported in HTTP client
>>> libraries, and much less hassle to
On 14 Sep 2011, at 18:26, Stephan Beal wrote:
> On Wed, Sep 14, 2011 at 7:24 PM, Stephan Beal wrote:
>> No, but for supporting clients which don't have cookies support. e.g. i've
>> written Java HTTP client apps (using a similar API to this one, actually)
>> but the client code doesn't support
On 11 Sep 2011, at 05:55, Stephan Beal wrote:
>
> In a JSON context, link-following is not an issue. There are no links, as
> such, in JSON docs - though individual JSON strings might incidentally
> contain HTML link strings, bots don't generically try to extract HTML text
> from JSON. Doing a
On 3 Sep 2011, at 14:05, Stephan Beal wrote:
> Hiya!
>
> Per the 'settings' page:
>
> "Settings marked with (v) are 'versionable' and will be overridden by the
> contents of files named .fossil-settings/PROPERTY."
>
> to use this, do i need to manually add the .fossil-settings files or are
On 2 Sep 2011, at 10:27, Dmitry Chestnykh wrote:
>
>> But should it be restricted to when compiling http_ssl? To Mac OS X? To 10.7?
>
> I think restricting it to just Mac OS X is okay.
>
> We know that they deprecated OpenSSL, and we don't have any plans to do
> something with it apart from ma
On 26 Aug 2011, at 21:31, Matt Welland wrote:
> I have switched to the new "trunk" and I think it address the issue I had
> with symlinks (sent in separate mail). Thanks!
>
> The empty-dirs works as advertised but I have an enhancement request. If I
> specify a multilevel directory and the upp
On 15 Aug 2011, at 21:42, Matt Welland wrote:
> 2011/8/15 Lluís Batlle i Rossell
>> 3) The file interface offers most version capabilities currently, in fossil.
>> Easier to reach old version, allowing branching, branches of code may need
>> different settings (ignore glob?).
>>
> I have had th
On 12 Aug 2011, at 22:39, Mike Meyer wrote:
> On Fri, Aug 12, 2011 at 1:28 PM, Ben Summers wrote:
>> On 12 Aug 2011, at 20:44, Mike Meyer wrote:
>> > On Fri, Aug 12, 2011 at 12:33 PM, Alaric Snell-Pym
>> wrote:
>> >> -BEGIN PGP SIGNED MESSAGE-
&
On 12 Aug 2011, at 20:44, Mike Meyer wrote:
> On Fri, Aug 12, 2011 at 12:33 PM, Alaric Snell-Pym
> wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 08/12/2011 07:10 PM, Joshua Paine wrote:
>> > On 8/12/2011 1:50 PM, altufaltu wrote:
>> >> 1. Versioned settings: I'd prefer ha
On 12 Aug 2011, at 16:10, Alaric Snell-Pym wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 08/12/2011 04:04 PM, Ben Summers wrote:
>>
>> On 12 Aug 2011, at 15:54, Alaric Snell-Pym wrote:
>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>
On 12 Aug 2011, at 15:54, Alaric Snell-Pym wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 08/12/2011 11:47 AM, Ben Summers wrote:
>>
>> Richard has kindly indicated he is probably willing to merge the changes in
>> the ben-testing branch if t
On 12 Aug 2011, at 15:46, Joshua Paine wrote:
> On 8/12/2011 6:47 AM, Ben Summers wrote:
>> * Versionable settings
>
> +1 This looks like a good way to do this
Thank you! :-)
>
>> * Relative pathname listings
>
> I would really like to see this on by default.
Richard has kindly indicated he is probably willing to merge the changes in the
ben-testing branch if the community has no objections, after being asked for
any suggestions on improvements.
I'd particularly like input on how these should be documented, and the names
chosen for settings and com
On 10 Aug 2011, at 15:11, Stephan Beal wrote:
> On Wed, Aug 10, 2011 at 9:24 AM, Ben Summers wrote:
>> It sounds like the default should change, and those who really care should
>> adjust their web server.
>
> Just FYI: the vast majority of users do not have admin-
On 9 Aug 2011, at 22:14, Martin S. Weber wrote:
> So I wanted to use javadoc/scaladoc style documentation and take advantage of
> fossils embedded documentation -- I put the scaladoc under /docco and
> happily was going to http://server:port/repo/doc/trunk/docco/index.html - but
> there noscri
On 9 Aug 2011, at 18:15, Matt Welland wrote:
>
> **soapbox mode - feel free to stop reading :) **
>
> The list of things that chip away at making a case for using fossil in
> serious work (lots of geographically distributed developers with minimal
> communication channels and a complex project
On 4 Aug 2011, at 16:35, Stephan Beal wrote:
> Hi!
>
> i just updated to 83c032de7f1 and i'm getting:
>
> make: *** No rule to make target `src/../manifest.uuid', needed by
> `bld/VERSION.h'. Stop.
>
> i've done a 'make distclean' and './configure --prefix=$HOME'.
>
> is there something els
On 22 Jul 2011, at 13:09, Lluís Batlle i Rossell wrote:
> On Fri, Jul 22, 2011 at 12:36:33PM +0100, Ben Summers wrote:
>>
>> On 22 Jul 2011, at 12:03, Lluís Batlle i Rossell wrote:
>>
>>> On Sun, Jul 10, 2011 at 01:03:06PM -0400, Martin Gagnon wrote:
>>>
On 22 Jul 2011, at 12:03, Lluís Batlle i Rossell wrote:
> On Sun, Jul 10, 2011 at 01:03:06PM -0400, Martin Gagnon wrote:
>> Le 2011-07-10 à 11:05, Ben Summers a écrit :
>>> Answering the question about breaking existing scripts, the output is
>>> identical when used
On 21 Jul 2011, at 07:42, Steve Bennett wrote:
>
> On 20/07/2011, at 7:16 PM, Ben Summers wrote:
>
>>
>> I'm concerned that typing 'make' on obscure platforms builds subtly broken
>> binaries. For example, on Solaris, it'll build one whi
On 20 Jul 2011, at 12:54, Stephan Beal wrote:
>
> On Wed, Jul 20, 2011 at 11:16 AM, Ben Summers wrote:
>
>> I'm concerned that typing 'make' on obscure platforms builds subtly broken
>> binaries. For example, on Solaris, it'll build one which tr
I'm concerned that typing 'make' on obscure platforms builds subtly broken
binaries. For example, on Solaris, it'll build one which truncates your
passwords to 8 characters.
I propose that we whitelist platforms where the default Makefile is known to
work, and force the use of ./configure for
On 14 Jul 2011, Stephan Beal wrote:
>
> On Thu, Jul 14, 2011 at 9:11 AM, Ben Summers wrote:
>
>>
>> If I run the ./configure script, Solaris make (which isn't GNU make) will
>> ignore GNUmakefile and build a broken binary again!
>>
>
> The maint
On 13 Jul 2011, Martin Gagnon wrote:
> There's no a big issue here.. it's just a kind of philosophical question.
>
> I've notice that autosetup "./configure" will create a GNUmakefile instead
> of a Makefile. In my OpenBSD system, bsd make doesn't use the GNUMake file
> when I type "make". So if
On Sun, Jul 10, 2011 at 10:12:33AM -0400, Joshua Paine wrote:
> On 7/10/2011 9:11 AM, Ben Summers wrote:
> > $ fossil status
> > In sub-directory two:
> > ADDED world.txt
> > EDITED src/display.c
> > 1 other change. Use --show-all option to list all cha
When working on my project, the current directory is always a sub-directory of
the checkout root. Perhaps I'm too used to subversion, but I'm finding the
checkout root-relative listing rather confusing. You can't copy and paste a
filename to, say, an add command without having to think about re
>
> On Jun 14, 2011, at 13:45 , Alexander Vladimirov wrote:
>
>> actually autoconf requires GNU M4, and somehow tends to bring automake
>> and libtool to your system as well.
>
>
> Yeah, that's for the developers. But users just need to run the Bourne shell
> configure script.
As an intermed
Alexander Vladimirov wrote:
>
> I tried to convert my subversion repo to fossil today and encountered a
> problem.
> As I can tell, svn->git conversion went ok, as I don't see the problem in
> the resulting git repo itself.
> After doing "git fast-export --all | fossil import --git myrepo.fossil"
On Thu, 02 Jun 2011 16:27:16 -0700, Jan Danielsson wrote:
> On 06/02/11 22:05, Ben Summers wrote:
> > I've created a new branch, ben-testing, with the new features I've been
> > working on. I'm going to be using this version from now on to make sure
> &g
I've created a new branch, ben-testing, with the new features I've been working
on. I'm going to be using this version from now on to make sure it's well
tested before it's considered for merging into trunk. It adds:
* SSL client certificate support
* Versionable settings (eg specify ignor
Hello,
I've tidied up the versionable-settings branch, which also adds an empty-dirs
setting. I welcome feedback and testing -- if you can, let me know what you
think, and any bugs you find.
http://fossil-scm.org/index.html/timeline?r=versionable-settings
"fossil help settings" should tell
On 21 May 2011, at 18:29, Ben Summers wrote:
>
> As a first step, I've made an experimental patch to see what the reaction is,
> and whether the approach is worth tidying up:
> ...
> * "Versionable" settings
> ...
> * empty-dirs setting
I've creat
Hello,
I've been using fossil for a few repos, and I really like the system. I'm about
to move my final repo to it, but it's quite a big project and will require a
bit of work to fit in with fossil. In particular, it assumes the SCM supports
empty directories and symlinks. Also, in my current
On 16 May 2011, at 21:42, Ben Summers wrote:
>
> I'm getting login failed errors when attempting to clone a repo over https on
> Solaris 10, but the same command and repo works fine on Mac OS X. Cloning the
> repo over http from the Mac works fine. The https server is running
Hello,
I'm getting login failed errors when attempting to clone a repo over https on
Solaris 10, but the same command and repo works fine on Mac OS X. Cloning the
repo over http from the Mac works fine. The https server is running Solaris 10
and the Jetty web server. Sessions below.
I'd appre
I've written a quick blog post on how to convert simple subversion repositories
to fossil as the info didn't seem to be readily out there:
http://bens.me.uk/2011/convert-simple-svn-to-fossil
I did discover something which might be a bug. If you don't include the
"--full-tree" on the git fast
On 10 May 2011, at 13:00, Richard Hipp wrote:
> On Mon, May 9, 2011 at 6:21 PM, Richard Hipp wrote:
>
>>
>>
>> On Mon, May 9, 2011 at 5:22 PM, Konstantin Khomoutov <
>> flatw...@users.sourceforge.net> wrote:
>>
>>> The console in Cyrillic Windows does really use two completely different
>>>
46 matches
Mail list logo
