On Wed, 5 Dec 2012 08:40:14 -0500, Richard Hipp
d...@sqlite.org wrote:
On Wed, Dec 5, 2012 at 8:38 AM, Lluís Batlle i Rossell vi...@viric.namewrote:
On Wed, Dec 05, 2012 at 01:51:51PM +0100, Gilles wrote:
Since this thread is a bit long, I'd like to ask: At this point, what
is the solution
On Sun, 27 Jan 2013 10:45:28 -0700
David Blanford d...@daveandval.org wrote:
Hello,
I am new to Fossil.
I have a fossil repository set at chiselapp. Cloned it so I have a
local repository as well. Everything was working perfectly. Now the
password seems to have changed. This is the
On Mon, Jan 28, 2013 at 10:21:03AM +0100, Gilles wrote:
On Wed, 5 Dec 2012 08:40:14 -0500, Richard Hipp
d...@sqlite.org wrote:
On Wed, Dec 5, 2012 at 8:38 AM, Lluís Batlle i Rossell
vi...@viric.namewrote:
On Wed, Dec 05, 2012 at 01:51:51PM +0100, Gilles wrote:
Since this thread is a
On Mon, 28 Jan 2013 10:43:19 +0100, Lluís Batlle i Rossell
vi...@viric.name wrote:
What do you mean by deconstruct? Checking files out?
As this question goes to me...
$ fossil help deconstruct
Thanks. After running deconstruct, do you just grep through all the
files, regardless of whether they
On Mon, Jan 28, 2013 at 11:01:32AM +0100, Gilles wrote:
On Mon, 28 Jan 2013 10:43:19 +0100, Lluís Batlle i Rossell
vi...@viric.name wrote:
What do you mean by deconstruct? Checking files out?
As this question goes to me...
$ fossil help deconstruct
Thanks. After running deconstruct, do
On Sat, Nov 24, 2012 at 3:21 PM, Richard Hipp d...@sqlite.org wrote:
One big problem here is that the user will doubtless expect to have full
Perl regular expressions. That will mean another compile-time dependency.
And maybe also a run-time dependency if a shared library is used (as most
On Mon, Jan 28, 2013 at 6:15 AM, Stephan Beal sgb...@googlemail.com wrote:
On Sat, Nov 24, 2012 at 3:21 PM, Richard Hipp d...@sqlite.org wrote:
One big problem here is that the user will doubtless expect to have full
Perl regular expressions. That will mean another compile-time dependency.
On Mon, 28 Jan 2013 12:15:22 +0100, Stephan Beal sgb...@googlemail.com
wrote:
On Sat, Nov 24, 2012 at 3:21 PM, Richard Hipp d...@sqlite.org wrote:
One big problem here is that the user will doubtless expect to have full
Perl regular expressions. That will mean another compile-time
On Mon, Jan 28, 2013 at 7:20 AM, Richard Hipp d...@sqlite.org wrote:
On Sun, Jan 27, 2013 at 9:18 AM, Gilles gilles.gana...@free.fr wrote:
So it looks like fossil ls branch name doesn't actually list the
files in the branch but rather the files in the branch currently
active (and its
On Mon, Jan 28, 2013 at 7:24 AM, j. van den hoff
veedeeh...@googlemail.comwrote:
On Mon, 28 Jan 2013 12:15:22 +0100, Stephan Beal sgb...@googlemail.com
wrote:
I'm quite sure that this is _not_ a standard regexp lib, but rather lua's
own (and somewhat different) substitute, called lua
On Mon, 28 Jan 2013 07:15:13 -0500, Richard Hipp
d...@sqlite.org wrote:
Fossil already has
http://www.fossil-scm.org/fossil/artifact/c8fb75a1615f?ln=21-23 and the
test-grep command.
test-grep doesn't show up with fossil help * in my 1.24. Was it
added recently and not yet available in the Windows
On Mon, 28 Jan 2013 15:25:19 +0100
Gilles gilles.gana...@free.fr wrote:
On Mon, 28 Jan 2013 11:22:11 +0100, Lluís Batlle i Rossell
vi...@viric.name wrote:
Is there a way to avoid writing all those files to disk, and just
output data to STDOUT and read this with grep?
I don't know how to
On Mon, Jan 28, 2013 at 10:27 AM, Gilles gilles.gana...@free.fr wrote:
On Mon, 28 Jan 2013 07:15:13 -0500, Richard Hipp
d...@sqlite.org wrote:
Fossil already has
http://www.fossil-scm.org/fossil/artifact/c8fb75a1615f?ln=21-23 and the
test-grep command.
test-grep doesn't show up with fossil
On Mon, Jan 28, 2013 at 08:50:56AM -0500, Richard Hipp wrote:
The regular expression matching in
www.fossil-scm.org/fossil/artifact/c8fb75a1615f is also lightweight and it
supports | and it is usually as fast or faster than grep in my tests
(though there are some cases for which grep is
Cool! I never thought to use a straight copy of my repo.
Eduardo Morras emorr...@yahoo.es wrote...
Perhaps what you want is a simply raw copy of the repository file,
it will keep all users and other sensitive information and after that
you can use sync, or pullpush.
After cloning, I
On Mon, 28 Jan 2013 17:34:44 +0100, Joerg Sonnenberger
jo...@britannica.bec.de wrote:
On Mon, Jan 28, 2013 at 08:50:56AM -0500, Richard Hipp wrote:
The regular expression matching in
www.fossil-scm.org/fossil/artifact/c8fb75a1615f is also lightweight and
it
supports | and it is usually as
On Mon, Jan 28, 2013 at 06:09:57PM +0100, j. van den hoff wrote:
On Mon, 28 Jan 2013 17:34:44 +0100, Joerg Sonnenberger
jo...@britannica.bec.de wrote:
On Mon, Jan 28, 2013 at 08:50:56AM -0500, Richard Hipp wrote:
The regular expression matching in
On Mon, 28 Jan 2013 18:22:42 +0100, Joerg Sonnenberger
jo...@britannica.bec.de wrote:
On Mon, Jan 28, 2013 at 06:09:57PM +0100, j. van den hoff wrote:
On Mon, 28 Jan 2013 17:34:44 +0100, Joerg Sonnenberger
jo...@britannica.bec.de wrote:
On Mon, Jan 28, 2013 at 08:50:56AM -0500, Richard Hipp
2013/1/28 Richard Hipp d...@sqlite.org
I haven't yet figure out the right syntax for doing a grep of files in the
repository. The implementation should be relatively easy once the right
interface is designed. Suggestions are welcomed.
I think there are three use cases: (1) searching
On Mon, Jan 28, 2013 at 1:30 PM, Petr P petr@gmail.com wrote:
2013/1/28 Richard Hipp d...@sqlite.org
I haven't yet figure out the right syntax for doing a grep of files in
the repository. The implementation should be relatively easy once the
right interface is designed. Suggestions
On Mon, Jan 28, 2013 at 07:26:32PM +0100, j. v. d. hoff wrote:
On Mon, 28 Jan 2013 18:22:42 +0100, Joerg Sonnenberger
jo...@britannica.bec.de wrote:
On Mon, Jan 28, 2013 at 06:09:57PM +0100, j. van den hoff wrote:
On Mon, 28 Jan 2013 17:34:44 +0100, Joerg Sonnenberger
On Mon, Jan 28, 2013 at 1:40 PM, Joerg Sonnenberger jo...@britannica.bec.de
wrote:
You don't understand me. Anchoring helps, if you can use it to avoid
initial wild cards or limit the length of backtracking. It doesn't help
to avoid the exponential edge cases with .*foo patterns though.
I
On Sat, 26 Jan 2013 19:04:26 -0800
Edward Berner e...@bernerfam.com wrote:
Yes, I use Fossil on Windows NT 4.0...
...
... The attached patch modifies
winhttp.c to load the offending functions at run time and only call
them if they actually exist.
Bravo! Someone get that man a sandwich.
On Mon, 28 Jan 2013 19:46:13 +0100, Richard Hipp d...@sqlite.org wrote:
On Mon, Jan 28, 2013 at 1:40 PM, Joerg Sonnenberger
jo...@britannica.bec.de
wrote:
You don't understand me. Anchoring helps, if you can use it to avoid
initial wild cards or limit the length of backtracking. It
On Mon, 28 Jan 2013 19:40:17 +0100, Joerg Sonnenberger
jo...@britannica.bec.de wrote:
On Mon, Jan 28, 2013 at 07:26:32PM +0100, j. v. d. hoff wrote:
On Mon, 28 Jan 2013 18:22:42 +0100, Joerg Sonnenberger
jo...@britannica.bec.de wrote:
On Mon, Jan 28, 2013 at 06:09:57PM +0100, j. van den
On Mon, 28 Jan 2013 19:46:13 +0100, Richard Hipp d...@sqlite.org wrote:
I think another point is that the Lua regexp does not do anchoring (or at
least I didn't see it - did I miss something?)
see also here (from http://www.lua.org/pil/20.4.html):
Usually, pattern matching is efficient
On Mon, Jan 28, 2013 at 08:35:57PM +0100, j. v. d. hoff wrote:
this would not prevent,
that people run into the exponential run time problem when using the
naive pattern instead the anchored one, but this could be
explained by a FAQ entry making
the problem practically irrelevant. or do I
A while back I ran into an issue where baseurl wasn't being handled
properly for the case where a single fossil server was handling multiple
repositories. For example, with:
fossil server /home/fossil --baseurl https://cowlark.com/
...then when $baseurl was being expanded in the templates, it
I haven't read all of the messages in this thread so please pardon the top
post and possible useless or redundant info but my lazy and oh so very
wrong method of grepping an entire fossil repo is to use fossil export and
some grepping. No need to put the whole expanded repo on disk.
First find
Sorry, didn't paste in the second grep:
fsl export | grep -A 10 -B 10 :1906
On Tue, Jan 29, 2013 at 12:08 AM, Matt Welland estifo...@gmail.com wrote:
I haven't read all of the messages in this thread so please pardon the top
post and possible useless or redundant info but my lazy and oh so
On Tue, 29 Jan 2013 00:10:26 -0700, Matt Welland
estifo...@gmail.com wrote:
Sorry, didn't paste in the second grep:
Thanks for contributing this work-around. I guess it shows that
there's a need for an easy, integrated grep to find code in the
repository.
31 matches
Mail list logo
