Brian Smith writes:
Hi All,
I've been playing with fossil for a few weeks now and I've come to
quite like it.
I was a tad disappointed that a git import tool hadn't been written
so, I went ahead and did that.
You can find the tool at:
pasqualinoferrentino-fos...@yahoo.it writes:
Conclusions.
The size winner is git, but only with the gc --aggressive command,
Well, just after sending this message I thought that I could try
another approach, I wanted to find a theoretical low limit of the
project size.
On Thu, Mar 4, 2010 at 1:38 PM, D. Richard Hipp d...@hwaci.com wrote:
Fossil repositories do not normally need to be vacuumed. The
exception is when they have been newly constructed such as by clone -
which vacuums automatically, or by the Git import tool. (Does that
Git import tool vacuum
Brian Smith writes:
I notice that the number you give and the number fossil reports don't
quite match up. Did the conversion happen correctly? If not would you
be willing to share some details about the repository (# of branches,
# of tags, # of merges (in particular merges involving
I'm sorry to bother w such a basic question, this is my first time using
a cms, and I will need one for a project that will begin shortly,
i don't want to move to testing other cms's, and I'm hoping to get this
running.
I've downloaded fossil, created a new rep, added committed files .
Next I
On Mar 4, 2010, at 7:26 PM, vannia wrote:
I'm sorry to bother w such a basic question, this is my first time
using
a cms, and I will need one for a project that will begin shortly,
i don't want to move to testing other cms's, and I'm hoping to get
this
running.
I've downloaded
6 matches
Mail list logo
