On Tue, Apr 14, 2015 at 6:49 AM, Gour g...@atmarama.net wrote:
Fossil's admin provides UI for shunning, but I'm looking for some shortcut
to
quickly shun most of those 6K files?
For this type of repo i would suggest replacing it with a fresh one.
Presumably the history isn't all that
On 4/14/15, Gour g...@atmarama.net wrote:
The last version of my *.gnucash file is 6.8M, while the ledger file is
~700K and I actually need only to keep that single file under Fossil, so I
wonder if there is some way to do 'massive shunning' of all those old
gncuash's tmp/log files in order
2015-04-14 5:46 GMT+02:00 Andy Bradford amb-fos...@bradfords.org:
Thanks. One thing to note is that I extended the function
fossil_find_nearest_fork to be able to work without checking the vmerge
table which is only available for a repository that is open, however,
fossil
Thus said Jan Nijtmans on Tue, 14 Apr 2015 16:36:18 +0200:
2) The additional time spent in the fork-detection is negligible.
I too was concerned about the additional time that might be spent
checking and whether or not it would be worth the extra time. Thanks for
taking the time to
On Tue, Apr 14, 2015 at 3:11 PM, Andy Bradford amb-fos...@bradfords.org
wrote:
What if the fork is intentially left unhandled? This means that all
parties will be alerted to the fact that there exists a fork because it
was intentionally left a fork. Is this acceptable? Will this
In short, if there are no false positive notifications on forks the fallout
from this change should really be very minimal and the benefits for those
who need it are substantial.
The long-winded response:
Mark Twain said it well, “I've lived through some terrible things in my
life, some of which
6 matches
Mail list logo
