IIUC:
you: fossil clone http://sqlite.org:8080 fossils/sqlite.fsl; cd
project_dir; fossil open ~/project_dir/sqlite.fsl; fossil server
Each of your our co-conspirators: fossil clone
http://your.machine.address:8080 fossils/sqlite.fsl; cd project_dir; fossil
open ~/fossils/sqlite.fsl
You will: fo
Hi,
Let's say I want to do this setup:
Clone sqlite repo on a local server
Then clone the server into several machines, with the users pushing changes
Then, someday, I will want to update my sqlite "base" code.
In git, one would first fork the code from another repo, add a second
remote:
git rem
Thus said Stephan Beal on Fri, 30 May 2014 22:25:30 +0200:
> H. It seems fossil no longer has an option to create the initial
> checkin.
It does using the --date-override option:
fossil new --date-override '2014-05-30 00:00:00' test.fossil
Will create a new fossil with an initial empty ch
Thus said Michai Ramakers on Fri, 30 May 2014 21:06:36 +0200:
> michai@main:~/proj/081/adm$ f ci -m 'added note about spent time'
> time_spent.txt
> New_Version: 187aa4a7c8b1377ddf05b1d979afe89adeff8dc0
> working checkout does not match what would have ended up in the
> repository: 9b324cf4c9c5b
No hurry - i won't be back on the pc until tomorrow evening. The wife's
attention takes priority, in any case!
"If at first I don't succeed... my wife will never let me forget it."
(recently heard in a video game)
(sent from a mobile device - please excuse brevity, typos, and top-posting)
-
On 30 May 2014 18:43, Stephan Beal wrote:
> On Fri, May 30, 2014 at 2:29 PM, Stephan Beal wrote:
>>
>> That's likely a misinteraction with the "all" setup and "close." When
>> fossil opens a repo db, it automatically records it in the global config db
>> for 'all' purposes. The close command "sho
On 30 May 2014 22:25, Stephan Beal wrote:
> On Fri, May 30, 2014 at 10:15 PM, Stephan Beal
> wrote:
>>
>> Is this repo _completely_ empty (no initial checkin)? If so, please
>> recreate it with an initial empty checkin and i'll bet my left leg the
>> problem goes away. If it is _not_ a completely
On Fri, May 30, 2014 at 10:15 PM, Stephan Beal
wrote:
> Is this repo _completely_ empty (no initial checkin)? If so, please
> recreate it with an initial empty checkin and i'll bet my left leg the
> problem goes away. If it is _not_ a completely empty repo then i'm at a
> loss.
>
H. It seems
On Fri, May 30, 2014 at 9:23 PM, Michai Ramakers
wrote:
> On 30 May 2014 21:13, Richard Hipp wrote:
> > Is the offending file a symbolic link?
>
> I don't think it's the contents of this or the other files causing this:
>
> michai@main:~/proj/081$ echo kiwi > kiwi
> michai@main:~/proj/081$ f add
On Fri, May 30, 2014 at 9:11 PM, Michai Ramakers
wrote:
> michai@main:~/proj/081$ f timeline
> +++ no more data (0) +++
>
> This is a brand new repo; indeed there are no checkins.
>
*cough* this looks _exactly_ like a bug we had recently involving the rid 0
(no checkins) case. i don't remember t
On Fri, May 30, 2014 at 9:33 PM, Warren Young wrote:
> On 5/30/2014 11:23, Stephan Beal wrote:
>
>>
>> a) pi is using an external USB 2.0 drive here because compiling anything
>> on a SD card is just too pokey.
>>
>
> Rotating media or SSD?
>
Plain old cheap spinning disk. i don't want to migrat
On 30 May 2014 21:27, Richard Hipp wrote:
>
> The proximal cause of the error message is the pre-commit sanity checks that
> Fossil runs on each check-in. (See
> http://www.fossil-scm.org/fossil/doc/tip/www/selfcheck.wiki for details.)
> Fossil is looking at the files it is about to commit, and c
On 5/30/2014 11:23, Stephan Beal wrote:
a) pi is using an external USB 2.0 drive here because compiling anything
on a SD card is just too pokey.
Rotating media or SSD?
Did you use the same external HDD on the laptop, or did it have an
unfair advantage in its internal drive?
b) These "f-xy
On Fri, May 30, 2014 at 3:23 PM, Michai Ramakers
wrote:
> On 30 May 2014 21:13, Richard Hipp wrote:
> > Is the offending file a symbolic link?
>
> I don't think it's the contents of this or the other files causing this:
>
> michai@main:~/proj/081$ echo kiwi > kiwi
> michai@main:~/proj/081$ f add
On 30 May 2014 21:13, Richard Hipp wrote:
> Is the offending file a symbolic link?
I don't think it's the contents of this or the other files causing this:
michai@main:~/proj/081$ echo kiwi > kiwi
michai@main:~/proj/081$ f add kiwi
ADDED kiwi
michai@main:~/proj/081$ f ci -m 'fossil bughunt test
On 30 May 2014 21:13, Richard Hipp wrote:
> Is the offending file a symbolic link?
no:
-rw-r--r-- 1 michai users 163 May 30 20:42 time_spent.txt
nor are there any symlinks in the path leading to the file or repo.
If interested: the repo is about 53 kB; I could mail it for analysis.
Michai
_
Is the offending file a symbolic link?
On Fri, May 30, 2014 at 3:11 PM, Michai Ramakers
wrote:
> and...
>
> michai@main:~/proj/081$ f timeline
> +++ no more data (0) +++
>
> This is a brand new repo; indeed there are no checkins.
>
> Michai
>
> On 30 May 2014 21:06, Michai Ramakers wrote:
> >
and...
michai@main:~/proj/081$ f timeline
+++ no more data (0) +++
This is a brand new repo; indeed there are no checkins.
Michai
On 30 May 2014 21:06, Michai Ramakers wrote:
> Hello,
>
> some weirdness I have not seen before:
>
> michai@main:~/proj/081/adm$ f changes
> ADDED time_spent.t
Hello,
some weirdness I have not seen before:
michai@main:~/proj/081/adm$ f changes
ADDED time_spent.txt
ADDED ../comm/20140530_sent_to_ec/indicator-B_Cu.pho
ADDED ../comm/20140530_sent_to_ec/indicator-B_Mask.pho
ADDED ../comm/20140530_sent_to_ec/indicator-Edge_Cuts.pho
ADDED
On Wed, May 14, 2014 at 5:55 PM, Stephan Beal wrote:
> Would this strategy server your purpose:
>
> - add a (-format FORMAT) option to (wiki commit).
>
> - if no format is specified, use the format from the prior version (if
> there is one), defaulting to fossil-wiki if no prior version is set or
On Fri, May 30, 2014 at 10:20 AM, Stephan Beal
wrote:
> On Fri, May 30, 2014 at 3:36 AM, Warren Young wrote:
>
>> How much work does this test do compared to normal user operations? Say,
>> a normal checkin, or a pull of the /tree URL from "fossil server"?
>>
>
> Excellent question: the timing i
On Fri, May 30, 2014 at 8:30 AM, Stephan Beal wrote:
>
> On Fri, May 30, 2014 at 2:28 PM, Michai Ramakers
> wrote:
>
>> Could anyone give an example of when it makes sense to clone a repo on
>> localhost at all, assuming it ever makes sense..? (I am currently
>>
>
> i can only think of one (smal
On Fri, May 30, 2014 at 2:29 PM, Stephan Beal wrote:
> That's likely a misinteraction with the "all" setup and "close." When
> fossil opens a repo db, it automatically records it in the global config db
> for 'all' purposes. The close command "should" (but apparently doesn't?)
> remove that file
Thus said Ron Wilson on Fri, 30 May 2014 09:42:44 -0400:
> As I recall, the 2 options have slightly different affects.
> "pull-only" only affects auto sync, while "dont-push" affects both
> manual and auto sync. A manual push will, of course, still push.
``pull-only'' pertains onl
On Fri, May 30, 2014 at 5:55 AM, Martin Gagnon wrote:
> Le 29 mai 2014 16:10, "Stephan Beal" a écrit :
>
> >
> > Wasn't even aware of pull-only until earlier today.
>
> snip
>
> Same for me, I always use autosync=1 together with the dont-push=1 setting
> for that. Look like an option got adde
On Fri, May 30, 2014 at 3:02 PM, Michai Ramakers
wrote:
> ok, found another small reason having to do with permissions, perhaps
> related with yesterday's thread about permissions. Without looking, I
> guess tempfiles (journal-related?) are being written in the repo-dir,
> is that so?
>
Good poi
On 30 May 2014 14:28, Michai Ramakers wrote:
>
> Could anyone give an example of when it makes sense to clone a repo on
> localhost at all, assuming it ever makes sense..? (I am currently
> cleaning up various scripts and dirs here, and a lot of sillyness
> shows up :)
ok, found another small rea
On 30 May 2014 14:29, Stephan Beal wrote:
> On Fri, May 30, 2014 at 2:24 PM, Michai Ramakers
> wrote:
>
>> I have only recently started using 'fossil all', and notice that
>> 'fossil all ls -c' (i.e. list checkouts) still show checkout-roots
>> that have been closed.
>
> That's likely a misintera
On Fri, May 30, 2014 at 2:28 PM, Michai Ramakers
wrote:
> Could anyone give an example of when it makes sense to clone a repo on
> localhost at all, assuming it ever makes sense..? (I am currently
>
i can only think of one (small) reason: to avoid having to know the path to
the repo file. Functi
On Fri, May 30, 2014 at 2:24 PM, Michai Ramakers
wrote:
> a related issue has come up here at least one: is there any real use
> for 'fossil close' of a repo?
>
Rarely. i can count on one hand the number of times i've used it since
2008. You can get the same effect with:
rm -f .fslckout _FOSSIL
Hello,
I asked a while ago about apparent slowness when cloning a repo on the
localhost (using 'http://localhost/...', because a script happened to
work like that).
Could anyone give an example of when it makes sense to clone a repo on
localhost at all, assuming it ever makes sense..? (I am curre
Hello,
a related issue has come up here at least one: is there any real use
for 'fossil close' of a repo?
I have only recently started using 'fossil all', and notice that
'fossil all ls -c' (i.e. list checkouts) still show checkout-roots
that have been closed.
I always used the 'close' command,
On Fri, May 30, 2014 at 11:55 AM, Martin Gagnon wrote:
> Same for me, I always use autosync=1 together with the dont-push=1 setting
> for that. Look like an option got added by someone that didn't know about
> the other.
>
LOL - wasn't aware of dont-push, either ;)
--
- stephan beal
http:/
Le 29 mai 2014 16:10, "Stephan Beal" a écrit :
>
> Wasn't even aware of pull-only until earlier today.
snip
Same for me, I always use autosync=1 together with the dont-push=1 setting
for that. Look like an option got added by someone that didn't know about
the other.
--
Martin G.
___
On Fri, May 30, 2014 at 3:36 AM, Warren Young wrote:
> PowerPC does some strange things with char, too. You might have fixed
> that in passing.
>
Very possibly. The bug was that i assumed (despite knowing better, deep
down) that (char) is signed, but C does not specify its signedness. i had
use
35 matches
Mail list logo
