On Mon, May 25, 2015 at 2:30 PM, Richard Hipp d...@sqlite.org wrote:
How many files are in a single check-out.
The working directory is made by 39k files, but around 3k are in the
repository (the others are blobs and not versioned files).
Please send us the output of fossil dbstat
Here it
In the meantime I've tried to rebuild the repository:
% fossil rebuild /sviluppo/fossil/myrepo.fossil --analyze --vacuum
but it seems to me things are going worst:
% time fossil commit -m ... # 1 file
New_Version: 0001bcb31d7a9a982f8558e22e897afc648ee5ff
fossil commit -m 24,43s user 6,36s
Most likely it's the checksum calculation of the checked-in files that is
slowing things down for you.
Do 'fossil set repo-cksum 0' and then try committing again.
Original Message
From: Luca Ferrari
Sent: Tuesday, 26 May 2015 19:37
To: Fossil SCM user's discussion
Reply To: Fossil SCM
On Tue, May 26, 2015 at 8:22 AM, Luca Ferrari fluca1...@infinito.it wrote:
On Mon, May 25, 2015 at 2:30 PM, Richard Hipp d...@sqlite.org wrote:
How many files are in a single check-out.
The working directory is made by 39k files, but around 3k are in the
repository (the others are blobs and
On 5/26/15, Luca Ferrari fluca1...@infinito.it wrote:
In the meantime I've tried to rebuild the repository:
% fossil rebuild /sviluppo/fossil/myrepo.fossil --analyze --vacuum
but it seems to me things are going worst:
% time fossil commit -m ... # 1 file
New_Version:
On Tue, May 26, 2015 at 06:57:18AM -0400, Richard Hipp wrote:
On 5/26/15, Luca Ferrari fluca1...@infinito.it wrote:
In the meantime I've tried to rebuild the repository:
% fossil rebuild /sviluppo/fossil/myrepo.fossil --analyze --vacuum
but it seems to me things are going worst:
%
Hi, I ran into this problem today, and I wasn't sure whether it was
better to make a ticket anonymously on fossil-scm.org or make a report
here. Please let me know if I made the wrong choice!
I have noticed some ... unexpected results regarding relative paths
before in fossil. An example is
On Mon, May 25, 2015 at 6:48 AM, Luca Ferrari fluca1...@infinito.it wrote:
Hi all,
I tried to move commits to another thread using tags but I was unable to
do it:
fossil tag add --propagate mybranch 455802dfc6
fossil tag cancel trunk 455802dfc6
but the timeline always shows me the commits
On 5/26/15, Will Parsons varro@nodomain.invalid wrote:
On Tuesday, 26 May 2015 3:20 PM -0400, Richard Hipp wrote:
On 5/26/15, Will Parsons varro@nodomain.invalid wrote:
Apparently a change was made to Fossil in February to issue warnings
about not being able to open /dev/null and
2015-05-26 20:46 GMT+02:00 Taylor Venable tay...@metasyntax.net:
Error #1: Moving existing files to curdir
RENAME a dir/a
RENAME b dir/b
cannot open /home/taylor/tmp/fossil/move/repo/dir/a for reading
Error #2: Moving non-existent files to curdir
SQLITE_ERROR: no such table: fmove
Apparently a change was made to Fossil in February to issue warnings
about not being able to open /dev/null and /dev/urandom. I'm running
a Fossil server from inetd under FreeBSD, and am getting these
messages when I go into Administration. Since I can't do anything
about the underlying reason
On 5/26/15, Will Parsons varro@nodomain.invalid wrote:
Apparently a change was made to Fossil in February to issue warnings
about not being able to open /dev/null and /dev/urandom. I'm running
a Fossil server from inetd under FreeBSD, and am getting these
messages when I go into
On Tuesday, 26 May 2015 3:20 PM -0400, Richard Hipp wrote:
On 5/26/15, Will Parsons varro@nodomain.invalid wrote:
Apparently a change was made to Fossil in February to issue warnings
about not being able to open /dev/null and /dev/urandom. I'm running
a Fossil server from inetd under
On Mon, May 25, 2015 at 5:02 AM, Luca Ferrari fluca1...@infinito.it wrote:
Great, this works!
Is there a way to make this inter-repository? I would not have to
redefine the report for every repository.
Fossil has a means to export/import configuration settings, see
14 matches
Mail list logo
