I would suggest running the problematic fossil command and capturing the
system call trace using 'strace -o LOG fossil cmd'. It's usually easy
enough to figure out the problem from the last dozen or so lines from the
'LOG' file.
Ge'
___
On Sun, Jan 30, 2011 at 11:28 PM, G. Clifford Williams
g...@notadiscussion.com wrote:
My apologies if this has been addressed already on the list, I don't get to
keep up as much as I'd like.
I've got several clients that manage config files via fossil (they're
moving from git). The repos
So, you are saying it is possible for multiple, independant Fossil
clients to share a single repository?
I had assumed that Fossil had some internal signaling mechanism to
allow command line invocations while fossil ui (or fossil server)
was running - not unlike how you can enter firefox
On Mon, Jan 31, 2011 at 7:23 PM, Ron Wilson ronw.m...@gmail.com wrote:
(If anyone is curious, within the software group, we are free to
manage our tools as we need - as long as our tools use only our PCs
and only use IT servers for file service. To run a server on an IT
server PC requires
On Mon, Jan 31, 2011 at 1:23 PM, Ron Wilson ronw.m...@gmail.com wrote:
So, you are saying it is possible for multiple, independant Fossil
clients to share a single repository?
Yes. I do that a lot, actually, though I typically have all the independent
Fossils running on the same machine so
On Mon, Jan 31, 2011 at 6:22 PM, Ron Wilson ronw.m...@gmail.com wrote:
On Mon, Jan 31, 2011 at 2:15 PM, Stephan Beal sgb...@googlemail.com
wrote:
On Mon, Jan 31, 2011 at 7:23 PM, Ron Wilson ronw.m...@gmail.com wrote:
and only use IT servers for file service. To run a server on an IT
On Mon, Jan 31, 2011 at 10:36:08AM -0500, Joshua Paine spake:
Just read your message again--I think you indicated that you're sharing a
single working copy over the network. That's kind of crazy, and not at all
recommended.
That's a bit pejorative and hyperbolic, don't you think?
My apologies if this has been addressed already on the list, I don't get to
keep up as much as I'd like.
I've got several clients that manage config files via fossil (they're moving
from git). The repos live on a network share (either NFS or CIFS). The problem
is that when the fossil is
8 matches
Mail list logo
