I am trying to use fossil to host a large(over 2G) source tree.
The add and commit is ok as long as individual source file is less than 1G.
but I can't close the big.fsl, the erro message is like following
fossil: not a valid repository: /export2/fossil.db/motopkg.fsl
I also created a ticket
Hi, stephan
Thanks for replying to my question again.
I may split up source tree into a few branches, but
What is biggest size a .fsl should limit to ?
So I can operate within the safe boundary.
Also I hope the warning of oversized .fsl should come out of the fossil
commands somehow.
I attempted to allow tbody, thead and tfoot in wikiformat.c but failed. I am
not understanding something. These elements are not really important to me but
using the cookbook setup for TinyMCE, it insists on inserting tbody tags which
are denied by the wiki format, thus, the TinyMCE integration
On Thu, Jan 7, 2010 at 4:32 PM, T.J. Yang tj_y...@hotmail.com wrote:
I may split up source tree into a few branches, but
What is biggest size a .fsl should limit to ?
_in theory_, the largest item which can portably be committed is somewhere
around 1.7GB. That number comes from:
a) max
Note that blobs are limited to 1G, so artifacts are limited to 1G
compressed, even on a 64-bit processor with 8GB of memory (I tried).
Gé
On 01/07/2010 08:15 AM, Stephan Beal wrote:
On Thu, Jan 7, 2010 at 4:32 PM, T.J. Yang tj_y...@hotmail.com
mailto:tj_y...@hotmail.com wrote:
I may
2010/1/8 Stephan Beal sgb...@googlemail.com
_in theory_, the largest item which can portably be committed is somewhere
around 1.7GB. That number comes from:
a) max memory space for 32-bit platforms = ~4GB. In my experience,
3.6-3.8GB is the max.
b) fossil does its diffs in memory, meaning 2
6 matches
Mail list logo
