On Jan 24, 2010, at 2:11 AM, Michael Richter wrote:
OK, maybe I'm being as thick as a whale sandwich, but when I try to
update my copy of fossil from fossil-scm.org, after downloading a
source tarball and compiling, I get the same login problem I had
with my earlier version:
Agreed, it probably counts as the easiest issue/bug tracker to setup
in the universe, despite the TCL-like embedded language.
Stephen
On Sunday, January 24, 2010, Ron Aaron r...@ronware.org wrote:
Fossil isn't only good for source-control!
I just set it up as a server on my local machine
Well, I also use fossil for file copy across my office laptop / home computer.
One is with domain login, other with no domain and many times windows copy just
doesn't work... may be because of firewall or some security app. But anyway,
fossil works better as optimized / compressed file copy and
Quoting Stephen De Gabrielle stephen.degabrie...@acm.org:
Agreed, it probably counts as the easiest issue/bug tracker to setup
in the universe, despite the TCL-like embedded language.
I was thinking that it's TCL-like embedded language was what made it
usable and so configurable. It's
I took a look at subversion, and it seems to use a single db/filesystem FSFS?
I'm guessing the same issues apply?
Cheers,
Stephen
On Friday, January 22, 2010, Stephen De Gabrielle
stephen.degabrie...@acm.org wrote:
Hi someone recently mentioned to me that they were uncomfortable with
their
Stephen De Gabrielle wrote:
I took a look at subversion, and it seems to use a single db/filesystem FSFS?
I'm guessing the same issues apply?
Hmmm ... at least if using the FSFS storage, a repository consists of a
lot of files. They can be backed up very comfortably as they are
immutable
Hi,
I like the simplicity and compactness of fossil and it seems a
perfect fit for a project. I just set up a fossil remote repo. I
gave no rights at all to Anon and Nobody. I added user Friend and
added rights to clone, check-out, check-in, etc. If I run fossil
clone
On Sun, 2010-01-24 at 15:35 -0500, D. Richard Hipp wrote:
Could this be a case of we've never done it that way before?
I think it's more a case of been there, done that, never want to do
it again. Just search for Berkeley DB usage leading to respository
corruption and data loss on the Wikipedia
8 matches
Mail list logo
