On Tue, Mar 15, 2011 at 5:40 PM, tr...@tekwissusa.com wrote:
Ok, I see. So having individual repositories is the better approach.
What about having a server vs just a file ?
e.g
fossil clone //server/repo.fossil repo.fossil
vs.
fossil clone http://server/repo:8080 repo.fossil
With a small
I'm rather new to fossil, but I've been using different VCS for almost 10
years.
I strongly recommend having a copy of the repository on each
station. Considering that disk space is cheap and the repo is small, maybe
less than 100M.
Furthermore you don't have a single point of failure on several
On Sun, Mar 13, 2011 at 5:46 PM, tr...@tekwissusa.com wrote:
I’d like to setup fossil for a very small in-house team (1 to 3 people).
There’s no need ever for having outside access, everything is private,
firewalled and trusted. So I was wondering if I can create a repository on a
file
Hi,
I have a general question about fossil and maybe even scm.
I’d like to setup fossil for a very small in-house team (1 to 3 people).
There’s no need ever for having outside access, everything is private,
firewalled and trusted. So I was wondering if I can create a repository on a
file
On Sun, Mar 13, 2011 at 5:46 PM, tr...@tekwissusa.com wrote:
Hi,
I have a general question about fossil and maybe even scm.
I’d like to setup fossil for a very small in-house team (1 to 3 people).
There’s no need ever for having outside access, everything is private,
firewalled and
5 matches
Mail list logo
