hi,
I found this statement in the `technical overview' section:
8-
When accessing the repository database using raw SQL and the fossil sql
command, the extension function content() with a single argument which
Hi,
I used to create my fossil repositories (scripted with
fossil init --admin-user $user $repo
But I just noticed that with 1.24, this does not work anymore, instead,
fossil will reply with:
Cannot figure out who you are! Consider using the --user
command line option, setting your
On Sat, Nov 24, 2012 at 5:40 AM, j. v. d. hoff veedeeh...@googlemail.comwrote:
hi,
I found this statement in the `technical overview' section:
8**--**
---
When accessing the repository database using raw SQL and
On Fri, 23 Nov 2012 07:14:37 -0500, Richard Hipp
d...@sqlite.org wrote:
Note that you can include multiple --tag options on a commit. When I
create a new release of SQLite, for example, I'll typically add a couple of
tags and a check-in specific background color, like this:
fossil commit -f
On Sat, 24 Nov 2012 13:12:38 +0100, Martin Gagnon eme...@gmail.com wrote:
On Sat, Nov 24, 2012 at 5:40 AM, j. v. d. hoff
veedeeh...@googlemail.comwrote:
hi,
I found this statement in the `technical overview' section:
8**--**
question: is there a straightforward (or sqlite-based) way to `grep'
through a specified file recursively backward in time through all
revisions (or until first hit of the search pattern)?
j.
ps: yes, I would know now (after having learned how to use `fossil
artifact' correctly...) how to
On Sat, Nov 24, 2012 at 7:57 AM, j. v. d. hoff veedeeh...@googlemail.comwrote:
question: is there a straightforward (or sqlite-based) way to `grep'
through a specified file recursively backward in time through all revisions
(or until first hit of the search pattern)?
j.
ps: yes, I would
On Sat, Nov 24, 2012 at 08:18:55AM -0500, Richard Hipp wrote:
On Sat, Nov 24, 2012 at 7:57 AM, j. v. d. hoff
veedeeh...@googlemail.comwrote:
question: is there a straightforward (or sqlite-based) way to `grep'
through a specified file recursively backward in time through all revisions
On Sat, 24 Nov 2012 14:18:55 +0100, Richard Hipp d...@sqlite.org wrote:
On Sat, Nov 24, 2012 at 7:57 AM, j. v. d. hoff
veedeeh...@googlemail.comwrote:
question: is there a straightforward (or sqlite-based) way to `grep'
through a specified file recursively backward in time through all
On Sat, Nov 24, 2012 at 8:34 AM, Lluís Batlle i Rossell vi...@viric.namewrote:
On Sat, Nov 24, 2012 at 08:18:55AM -0500, Richard Hipp wrote:
On Sat, Nov 24, 2012 at 7:57 AM, j. v. d. hoff
veedeeh...@googlemail.comwrote:
question: is there a straightforward (or sqlite-based) way to
On Sat, Nov 24, 2012 at 08:59:58AM -0500, Richard Hipp wrote:
On Sat, Nov 24, 2012 at 8:34 AM, Lluís Batlle i Rossell
vi...@viric.namewrote:
On Sat, Nov 24, 2012 at 08:18:55AM -0500, Richard Hipp wrote:
On Sat, Nov 24, 2012 at 7:57 AM, j. v. d. hoff
veedeeh...@googlemail.comwrote:
On Sat, 24 Nov 2012 14:59:58 +0100, Richard Hipp d...@sqlite.org wrote:
On Sat, Nov 24, 2012 at 8:34 AM, Lluís Batlle i Rossell
vi...@viric.namewrote:
On Sat, Nov 24, 2012 at 08:18:55AM -0500, Richard Hipp wrote:
On Sat, Nov 24, 2012 at 7:57 AM, j. v. d. hoff
On Sat, Nov 24, 2012 at 9:12 AM, j. v. d. hoff veedeeh...@googlemail.comwrote:
On Sat, 24 Nov 2012 14:59:58 +0100, Richard Hipp d...@sqlite.org wrote:
On Sat, Nov 24, 2012 at 8:34 AM, Lluís Batlle i Rossell vi...@viric.name
wrote:
On Sat, Nov 24, 2012 at 08:18:55AM -0500, Richard Hipp
On Sat, 24 Nov 2012 15:21:54 +0100, Richard Hipp d...@sqlite.org wrote:
On Sat, Nov 24, 2012 at 9:12 AM, j. v. d. hoff
veedeeh...@googlemail.comwrote:
On Sat, 24 Nov 2012 14:59:58 +0100, Richard Hipp d...@sqlite.org wrote:
On Sat, Nov 24, 2012 at 8:34 AM, Lluís Batlle i Rossell
On Sat, 24 Nov, j. v. d. hoff wrote:
I would like to issue something like `fossil artifact [1234] -f
myfile.txt'
I may be misunderstanding, but isn't
fossil finfo -p -r [1234] myfile.txt
what you want?
Greetings,
Stefan
--
Stefan Bellon
___
On Sat, 24 Nov 2012 15:43:57 +0100, Stefan Bellon sbel...@sbellon.de
wrote:
On Sat, 24 Nov, j. v. d. hoff wrote:
I would like to issue something like `fossil artifact [1234] -f
myfile.txt'
I may be misunderstanding, but isn't
fossil finfo -p -r [1234] myfile.txt
what you want?
yes
Le 2012-11-24 10:16, j. v. d. hoff a écrit :
On Sat, 24 Nov 2012 15:43:57 +0100, Stefan Bellon sbel...@sbellon.de
wrote:
On Sat, 24 Nov, j. v. d. hoff wrote:
I would like to issue something like `fossil artifact [1234] -f
myfile.txt'
I may be misunderstanding, but isn't
fossil finfo -p
On Sat, 24 Nov 2012 16:23:05 +0100, Martin Gagnon eme...@gmail.com wrote:
Le 2012-11-24 10:16, j. v. d. hoff a écrit :
On Sat, 24 Nov 2012 15:43:57 +0100, Stefan Bellon sbel...@sbellon.de
wrote:
On Sat, 24 Nov, j. v. d. hoff wrote:
I would like to issue something like `fossil artifact
On Sat, Nov 24, 2012 at 10:35 AM, j. v. d. hoff
veedeeh...@googlemail.comwrote:
On Sat, 24 Nov 2012 16:23:05 +0100, Martin Gagnon eme...@gmail.com
wrote:
Le 2012-11-24 10:16, j. v. d. hoff a écrit :
On Sat, 24 Nov 2012 15:43:57 +0100, Stefan Bellon sbel...@sbellon.de
wrote:
On Sat, 24
A grep though history would be a very useful functionality, There have been
many times I'd have used it. Using sqlite3 glob or like for the pattern
match would be more than adequate. If you need a regex just use the glob to
select for the lowest common denominator and then pipe though egrep with
Le 2012-11-24 11:40, Richard Hipp a écrit :
On Sat, Nov 24, 2012 at 10:35 AM, j. v. d. hoff
veedeeh...@googlemail.com mailto:veedeeh...@googlemail.com wrote:
On Sat, 24 Nov 2012 16:23:05 +0100, Martin Gagnon eme...@gmail.com
mailto:eme...@gmail.com wrote:
Le 2012-11-24 10:16,
On Sat, 24 Nov 2012 17:40:30 +0100, Richard Hipp d...@sqlite.org wrote:
On Sat, Nov 24, 2012 at 10:35 AM, j. v. d. hoff
veedeeh...@googlemail.comwrote:
On Sat, 24 Nov 2012 16:23:05 +0100, Martin Gagnon eme...@gmail.com
wrote:
Le 2012-11-24 10:16, j. v. d. hoff a écrit :
On Sat, 24 Nov
Am Samstag, 24. November 2012, 08:59:58 schrieb Richard Hipp:
So what should the output look like? Suppose we implement a command:
fossil grep REGEXP FILENAMEGLOB
Which searches all historical versions of files that match FILENAMEGLOB for
patterns that match REGEXP. Suppose for
On Sat, 24 Nov 2012 20:05:55 +0100, Bernd Paysan bernd.pay...@gmx.de
wrote:
Am Samstag, 24. November 2012, 08:59:58 schrieb Richard Hipp:
So what should the output look like? Suppose we implement a command:
fossil grep REGEXP FILENAMEGLOB
Which searches all historical versions of files
Am Samstag, 24. November 2012, 20:28:16 schrieb j. v. d. hoff:
what you propose could easily be filter out from a full recursive search
backward through all revisions (and it would require such a search), right?
Fossil, like many other VCSes, compresses revisions internally, and stores
only
Hello
Unless there's a way to call fossil.exe and know how the command
ended...
http://imageshack.us/photo/my-images/688/fossilprompt.jpg
... is there a way to recompile the Fossil source code to turn it into
a DLL* to get some feedback when calling Fossil programmatically?
Since
On Sat, Nov 24, 2012 at 3:20 PM, Gilles gilles.gana...@free.fr wrote:
Hello
Unless there's a way to call fossil.exe and know how the command
ended...
http://imageshack.us/photo/my-images/688/fossilprompt.jpg
... is there a way to recompile the Fossil source code to turn it into
On Sat, 24 Nov, Bernd Paysan wrote:
% fossil grep xyzzy ext1.txt
7c88a35016..cbaff03a91:ext1.txt:here we have the *xyzzy* string
I would be in favour of this approach for a version control system with
the concept of serial, incremental revision numbers where you can
deduce from a range N..M
On Sat, 24 Nov 2012 15:31:41 -0500, Richard Hipp
d...@sqlite.org wrote:
The current Fossil implementation is not appropriate for converting into a
library due to its extensive using of global variables and due to a
cavalier attitude toward freeing allocated memory. Fossil is designed to
run a
On Sat, 24 Nov 2012 09:21:54 -0500, 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
Stefan Bellon sbel...@sbellon.de wrote:
I'd rather vote for a list all matching revisions
in the --all case and the default behaviour to stop at the most recent
match.
I think there are three cases, the third being the earliest matching revision.
Especially if the current revision is a match.
What about just using regex(3)? It's included with BSD and quite
possibly Linux distributions, but I have no way of checking.
No idea how good the library is, but it might cut down on dependencies?
--
James Turner
ja...@calminferno.net
___
On Sat, Nov 24, 2012 at 5:02 PM, Gilles gilles.gana...@free.fr wrote:
On Sat, 24 Nov 2012 09:21:54 -0500, 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 Sun, 25 Nov 2012 00:17:44 +0100, j. v. d. hoff
veedeeh...@googlemail.com wrote:
would intgration of the lua library
http://www.lua.org/
be a silly idea? it's under MIT licence, has very small footprint (quite
probable smaller than a full fledged regex lib), and has a quite powerful
34 matches
Mail list logo
