Hello,
I first want to say what a terrific version control manager Fossil is!
I took my first serious look at Fossil last week and have already
converted a few of my personal projects away from 'git'. The built-in
bug tracker and wiki are genius touches! Thank you, Fossil community,
for your
On Fri, Feb 7, 2014 at 4:33 PM, Rich Neswold rich.nesw...@gmail.com wrote:
I don't have any question; I just thought I'd document my experiences.
Thanks for your feedback! IMO (possibly a minority opinion), Fossil has
never aspired to host repos quite as large as those. i remember the pkgsrc
On Fri, Feb 7, 2014 at 11:17 AM, Stephan Beal sgb...@googlemail.com wrote:
On Fri, Feb 7, 2014 at 4:33 PM, Rich Neswold rich.nesw...@gmail.comwrote:
I don't have any question; I just thought I'd document my experiences.
Thanks for your feedback! IMO (possibly a minority opinion), Fossil
On Fri, 7 Feb 2014 18:40:32 +0100
Stephan Beal sgb...@googlemail.com wrote:
It would be really cool to see someone implement their own SCM based
on fossil's core artifact model and their own db back-end, though.
What about Monotone? Linus was looking at it, but it was too slow at
that time.
On Fri, Feb 07, 2014 at 07:39:37PM +0100, Gour wrote:
On Fri, 7 Feb 2014 18:40:32 +0100
Stephan Beal sgb...@googlemail.com wrote:
It would be really cool to see someone implement their own SCM based
on fossil's core artifact model and their own db back-end, though.
What about Monotone?
On Fri, 7 Feb 2014 20:32:56 +0100
Lluís Batlle i Rossell vi...@viric.name
wrote:
It was a bug of monotone, that slowness. Fixed, for what I remember.
Yeah, too bad. Otherwise we wouldn't see git. :-)
But monotone works on sqlite, if the deal is sqlite.
Right, but I see Monotone's influence
On Fri, Feb 07, 2014 at 05:17:23PM +0100, Stephan Beal wrote:
i'd be interested in seeing the output of 'dbstat' on your repo, except
that it could take some time for it to finish generating its output (so
don't feel obligated to try it). Here's the info for the current fossil
core repo:
On Fri, Feb 7, 2014 at 6:15 PM, Ron Wilson ronw.m...@gmail.com wrote:
I am guessing this is a limitation of SQLite, which is designed to be
light. It would be interesting to see how Fossil would perform when
plugged in to, for example, PostgreSQL, MariaSQL or other heavy duty
SQL server. Of
On Fri, Feb 7, 2014 at 10:17 AM, Stephan Beal sgb...@googlemail.com wrote:
i'd be interested in seeing the output of 'dbstat' on your repo, except that
it could take some time for it to finish generating its output (so don't
feel obligated to try it). Here's the info for the current fossil core
On Fri, Feb 7, 2014 at 9:11 PM, Joerg Sonnenberger
jo...@britannica.bec.dewrote:
On Fri, Feb 07, 2014 at 05:17:23PM +0100, Stephan Beal wrote:
i'd be interested in seeing the output of 'dbstat' on your repo, except
that it could take some time for it to finish generating its output (so
On 2/8/2014 5:19 AM, Stephan Beal wrote:
It would be really cool
to see someone implement their own SCM based on fossil's core artifact
model and their own db back-end, though. It would likely require a complete
re-implementation, not just rewriting most of the SQL.
Wasn't Veracity
On Fri, Feb 7, 2014 at 11:40 AM, Stephan Beal sgb...@googlemail.com wrote:
On Fri, Feb 7, 2014 at 6:15 PM, Ron Wilson ronw.m...@gmail.com wrote:
I am guessing this is a limitation of SQLite, which is designed to be
light. It would be interesting to see how Fossil would perform when
plugged in
12 matches
Mail list logo
