Re: [fossil-users] how to deal with files which became directories?

On Tue, Jan 14, 2014 at 01:02:36AM -0500, Martin Gagnon wrote: > On Mon, Jan 13, 2014 at 10:51:18PM -0700, Christian Pekeler wrote: > >On Jan 13, 2014, at 15:21, Ron Wilson wrote: > > > > On Mon, Jan 13, 2014 at 3:18 PM, Christian Pekeler > > wrote: > > > > > I have a Numbers document in

Re: [fossil-users] TH1: set v 0; unset v; info exists v;

On Mon, 13 Jan 2014, Joe Mistachkin wrote: > > Sergei Gavrikov wrote: > > > > It looks like the same check is needed for Th_UnsetVar() too. > > > > Actually, the issue with Th_UnsetVar was slightly different; > however, it should be fixed now: > > http://www.fossil-scm.org/index.html/info

Re: [fossil-users] how to deal with files which became directories?

On Mon, Jan 13, 2014 at 10:51:18PM -0700, Christian Pekeler wrote: >On Jan 13, 2014, at 15:21, Ron Wilson wrote: > > On Mon, Jan 13, 2014 at 3:18 PM, Christian Pekeler > wrote: > > > I have a Numbers document in Fossil. It used to be just a file, now it's a > > folder. How can I commit t

Re: [fossil-users] how to deal with files which became directories?

On Jan 13, 2014, at 15:21, Ron Wilson wrote: > On Mon, Jan 13, 2014 at 3:18 PM, Christian Pekeler > wrote: > > I have a Numbers document in Fossil. It used to be just a file, now it's a > > folder. How can I commit this change to Fossil? > > > > > > > fossil rm Documents/daycare_stats.numbers >

[fossil-users] Idea: Distributing pre-compiled binary versions of selected development versions of Fossil

In http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg14284.html, Dr. Hipp wrote: "[...] As part of its role of supporting SQLite, Fossil serves as a test platform for the latest SQLite alphas. For that reason, I want Fossil 1.28 to have the very latest trunk of SQLite, not the mos

Re: [fossil-users] Version 1.28 release?

On Thu, Jan 9, 2014 at 8:20 AM, Richard Hipp wrote: It has been a few months since the last official release of Fossil. I > wonder if we should consider publishing trunk as the official version 1.28? > I realize I am responding to this a little late, but, hey, as a non-code-contributing blowhar

Re: [fossil-users] TH1: set v 0; unset v; info exists v;

Sergei Gavrikov wrote: > > It looks like the same check is needed for Th_UnsetVar() too. > Actually, the issue with Th_UnsetVar was slightly different; however, it should be fixed now: http://www.fossil-scm.org/index.html/info/1ebe4b02e4 Thanks again. -- Joe Mistachkin ___

Re: [fossil-users] fossil import timestamp mangling

On 12/22/13, 8:41 PM, David Given wrote: > On 22/12/13 20:18, Richard Hipp wrote: > [...] >> No. Look at the diff. The indentation is wrong. > > Oops, sorry. This one should fix it: > > http://www.fossil-scm.org/index.html/info/70b82e8cc5 Was there ever a decision on this? I'd rather like to g

Re: [fossil-users] how to deal with files which became directories?

On Mon, Jan 13, 2014 at 3:18 PM, Christian Pekeler wrote: > I have a Numbers document in Fossil. It used to be just a file, now it's a > folder. How can I commit this change to Fossil? > > > > fossil rm Documents/daycare_stats.numbers > DELETED Documents/daycare_stats.numbers > > fossil add Docume

Re: [fossil-users] Version 1.28 release?

On Thu, Jan 9, 2014 at 2:20 PM, Richard Hipp wrote: > It has been a few months since the last official release of Fossil. I > wonder if we should consider publishing trunk as the official version 1.28? > > -- > D. Richard Hipp > d...@sqlite.org > > ___

Re: [fossil-users] Tree view and browser back button

On Mon, Jan 13, 2014 at 03:54:34PM -0500, Richard Hipp wrote: >On Mon, Jan 13, 2014 at 3:51 PM, Martin Gagnon wrote: > > I like very much the new tree view but there's one thing that I found a > bit annoying. After clicking on a file that is deep in the directory > structure, t

Re: [fossil-users] Tree view and browser back button

On Mon, Jan 13, 2014 at 04:03:14PM -0500, James Turner wrote: > On Mon, Jan 13, 2014 at 03:54:34PM -0500, Richard Hipp wrote: > > On Mon, Jan 13, 2014 at 3:51 PM, Martin Gagnon wrote: > > > > > > > > I like very much the new tree view but there's one thing that I found a > > > bit annoying. After

Re: [fossil-users] Tree view and browser back button

On Mon, Jan 13, 2014 at 03:54:34PM -0500, Richard Hipp wrote: > On Mon, Jan 13, 2014 at 3:51 PM, Martin Gagnon wrote: > > > > > I like very much the new tree view but there's one thing that I found a > > bit annoying. After clicking on a file that is deep in the directory > > structure, the tree

Re: [fossil-users] Tree view and browser back button

On Mon, Jan 13, 2014 at 3:51 PM, Martin Gagnon wrote: > > I like very much the new tree view but there's one thing that I found a > bit annoying. After clicking on a file that is deep in the directory > structure, the tree become all collapsed again after pressing the back > button. > Chrome doe

[fossil-users] Tree view and browser back button

Hello, I like very much the new tree view but there's one thing that I found a bit annoying. After clicking on a file that is deep in the directory structure, the tree become all collapsed again after pressing the back button. I think it would be useful that tree state come back to how it was b

[fossil-users] how to deal with files which became directories?

I have a Numbers document in Fossil. It used to be just a file, now it's a folder. How can I commit this change to Fossil? > fossil stat ... NOT_A_FILE Documents/daycare_stats.numbers > ls -l Documents/daycare_stats.numbers total 504 drwxr-xr-x 2 pekeler staff 68 12 Jan 11:31 Data -rw-r--r

Re: [fossil-users] Multiple independent timelines in a fossil - how to create and what are the unintended consequences?

On Mon, Jan 13, 2014 at 10:56 AM, Jan Nijtmans wrote: > sqlite3 .fossil > sqlite3> UPDATE vvar SET value=0 WHERE name='checkout'; > sqlite3> DELETE from vmerge; > sqlite3> DELETE from vfile; > sqlite3> .exit > fossil commit --branch ... > Tricky,

Re: [fossil-users] TH1: set v 0; unset v; info exists v;

> > Sergei Gavrikov wrote: > > > As I could see Th_ExistsVar() does miss a test for pValue->zData > > > as Th_GetVar() does > > http://fossil-scm.org/index.html/artifact/a561c58c237b3eb43eaf55e6f9cc6a9b8a26e5d1?ln=1142-1149. It looks like the same check is needed for Th_UnsetVar() too. # Expect

Re: [fossil-users] SQLITE_ENABLE_EXPLAIN_COMMENTS recommended option? [Was: Version 1.28 release?]

2014/1/13 Jan Nijtmans : > Of course, I meant "makefile.wiki" Thanks! That was exactly my question. Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org ht

Re: [fossil-users] SQLITE_ENABLE_EXPLAIN_COMMENTS recommended option? [Was: Version 1.28 release?]

2014/1/13 Jan Nijtmans : > In that case, I think that "build.wiki" (and the comment in > SQLite) should be adapted accordingly. I have no opinion > whether it should be on or off, that's not my main point. Of course, I meant "makefile.wiki" Regards, Jan Nijtmans

Re: [fossil-users] SQLITE_ENABLE_EXPLAIN_COMMENTS recommended option? [Was: Version 1.28 release?]

2014/1/13 Richard Hipp : > Adding SQLITE_ENABLE_EXPLAIN_COMMENTS makes the output of EXPLAIN in the > shell much, much easier to read. Leave it turned on. In that case, I think that "build.wiki" (and the comment in SQLite) should be adapted accordingly. I have no opinion whether it should be on o

Re: [fossil-users] SQLITE_ENABLE_EXPLAIN_COMMENTS recommended option? [Was: Version 1.28 release?]

Adding SQLITE_ENABLE_EXPLAIN_COMMENTS makes the output of EXPLAIN in the shell much, much easier to read. Leave it turned on. On Mon, Jan 13, 2014 at 7:55 AM, Jan Nijtmans wrote: > Fossil's internal SQLite is currently compiled with the following > options (main.mk): > SQLITE_OPTIONS = -DSQLITE

[fossil-users] SQLITE_ENABLE_EXPLAIN_COMMENTS recommended option? [Was: Version 1.28 release?]

Fossil's internal SQLite is currently compiled with the following options (main.mk): SQLITE_OPTIONS = -DSQLITE_OMIT_LOAD_EXTENSION=1 \ -DSQLITE_ENABLE_LOCKING_STYLE=0 \ -DSQLITE_THREADSAFE=0 \ -DSQLITE_DEFAULT_FILE_FORMAT=4 \ -DSQL

Re: [fossil-users] Multiple independent timelines in a fossil - how to create and what are the unintended consequences?

2014/1/12 Matt Welland : > I've tested both these ideas and they appear to work. It does look like > shunning or removing the initial commit is needed or somehow the code sees a > connection between the trees. In my test half the files had no ancestor and > did not merge and half the files did merg