Update: fossil does work through the proxy.
Problem seems to be with the proxy, it gives 'bad request' error when user@ is
added to URL in POST method.
I'll work with IT folks for fixing it.
- Original Message -
From: altufa...@mail.com
Sent: 05/15/12 03:57 PM
To: Fossil SCM user's
Be aware that fossil uses cgi mode, even when in standalone server mode,
and that cgi does not support all request types (e.g. PUT and DELETE
iirc).
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
On May 15, 2012 12:28 PM, altufa...@mail.com wrote:
It seems
On Tue, May 15, 2012 at 06:20:28PM +0200, Stephan Beal wrote:
1.5) If you happen to know of a *flat-rate* mobile internet provider in
Germany, please let me know!
BILD.mobil might be the best option. They have pre-paid data cards for
around 7EUR / week, 1GB high speed. You might need someone in
On Tue, May 15, 2012 at 7:34 PM, Joerg Sonnenberger jo...@britannica.bec.de
wrote:
On Tue, May 15, 2012 at 06:20:28PM +0200, Stephan Beal wrote:
1.5) If you happen to know of a *flat-rate* mobile internet provider in
Germany, please let me know!
BILD.mobil might be the best option. They
Hi all,
Please consider the following test (in Linux on version 1.22):
% mkdir dir_a
% ln -s dir_a dir_b
% touch dir_a/foo
% fossil add dir_a/foo
ADDED dir_a/foo
% fossil commit dir_a/foo -m 'adding test'
ADDED dir_a/foo
...
% fossil ann dir_a/foo
% fossil ann dir_b/foo
fossil: no such
On Tue, May 15, 2012 at 7:51 PM, James Masters james.d.mast...@gmail.comwrote:
Hi all,
Please consider the following test (in Linux on version 1.22):
% ln -s dir_a dir_b
...
% fossil ann dir_a/foo
% fossil ann dir_b/foo
fossil: no such file: dir_b/foo
I realize that fossil probably
On Tue, May 15, 2012 at 1:51 PM, James Masters james.d.mast...@gmail.comwrote:
Hi all,
Please consider the following test (in Linux on version 1.22):
% mkdir dir_a
% ln -s dir_a dir_b
% touch dir_a/foo
% fossil add dir_a/foo
ADDED dir_a/foo
% fossil commit dir_a/foo -m 'adding test'
On Tue, May 15, 2012 at 8:00 PM, Richard Hipp d...@sqlite.org wrote:
% ln -s dir_a dir_b
I'm not following the confusion here. Fossil can only annotate files that
have been checked in and have history. You've never before checked in
dir_b/foo. It is
The key part is the symlink and
Accidentally replied off-list...
On Tue, May 15, 2012 at 7:56 PM, Stephan Beal sgb...@googlemail.com wrote:
dir_b/foo does not refer to a file it knows. Whether fossil _should_ or
_can_ resolve symlinks that way is a question we must wait for Richard to
answer, i suspect.
And i meant to
This will probably start a new thread... if so, then sorry... I have digest
mode enabled and it is not clear to me how to reply directly to a
particular thread when using the digest. Anyway, my response is below:
Message: 6
Date: Tue, 15 May 2012 14:00:43 -0400
From: Richard Hipp
On 5/15/12, James Masters james.d.mast...@gmail.com wrote:
Sorry, I missed the crucial step of adding and comitting dir_b as a
symlink. Please append this to my example above:
% fsl add dir_b
ADDED dir_b
% fsl commit dir_b -m 'adding symlink'
ADDED dir_b
...
% fsl ann dir_b/foo
On 15 May 2012 03:01, Ron Wilson ronw.m...@gmail.com wrote:
I would guess that Trac stores its wiki pages in version control, so
the main issue there would be Trac wiki markup vs Fossil (or other)
wiki markup. If there is a client side renderer for Trac's markup,
markup conversion would not be
On 15 May 2012 03:01, Ron Wilson ronw.m...@gmail.com wrote:
Trac's versioning for wiki and issues is native to Trac, and is used
solely for the wiki and issues. The version control of the source for
a project is entirely separate.
Trac does not use your source control choice for issues or
On Tue, May 15, 2012 at 10:23 PM, Scott Robison sc...@scottrobison.uswrote:
On 15 May 2012 03:01, Ron Wilson ronw.m...@gmail.com wrote:
Trac's versioning for wiki and issues is native to Trac, and is used
solely for the wiki and issues. The version control of the source for
a project is
14 matches
Mail list logo
