Hi,
Every time I open a fossil repo, even if I simply open it to just get a copy
of the files in some directory, I end up with a 'touched' repo file, as if
some 'write' operation has occurred in the database. And a binary compare
of before and after shows that some bytes actually change.
Thus said Tony Papadimitriou on Sat, 09 Aug 2014 20:01:30 +0300:
Every time I open a fossil repo, even if I simply open it to just get
a copy of the files in some directory, I end up with a 'touched' repo
file, as if some 'write' operation has occurred in the database.
Every time fossil
Subject: Re: [fossil-users] How to avoid 'touching' the fossil repo for
read-only operation?
Thus said Tony Papadimitriou on Sat, 09 Aug 2014 20:01:30 +0300:
Every time I open a fossil repo, even if I simply open it to just get
a copy of the files in some directory, I end up with a 'touched
On Sat, Aug 9, 2014 at 7:58 PM, Tony Papadimitriou to...@acm.org wrote:
* this seems kind of pointless, given I can open the same repo in multiple
locations at the same time. Are you sure you're not referring to the
separate _FOSSIL_ database, instead, or some special operation that changes
Thus said Tony Papadimitriou on Sat, 09 Aug 2014 20:58:41 +0300:
* it doesn't seem to be the actual reason as I ran your query on my
various fossils, and many of them return zero rows or very few rows
compared to the number of opens it went through so far.
If you close the
On Sat, Aug 9, 2014 at 8:26 PM, Andy Bradford amb-fos...@bradfords.org
wrote:
It looks like fossil ls does not honor the -R option---perhaps it
should?
Mine does ;)
[stephan@host:~/cvs/fossil/libfossil/s2]$ f-ls -R ../../cwal.fsl | head
File list from manifest version 'trunk'
6 matches
Mail list logo
