Re: [fossil-users] EXECUTABLE, and not really being added to updated repo

On Dec 6, 2016 19:18, "Andy Bradford" wrote: Thus said bch on Tue, 06 Dec 2016 14:46:23 -0800: > I've got a collection of files who's apparently only change is the > EXECUTABLE bit set, but after a commit, they're still showing up in "f > chan"; I retried w/ a

Re: [fossil-users] EXECUTABLE, and not really being added to updated repo

Thus said bch on Tue, 06 Dec 2016 14:46:23 -0800: > I've got a collection of files who's apparently only change is the > EXECUTABLE bit set, but after a commit, they're still showing up in "f > chan"; I retried w/ a --sha1sum switch; still listed as changed > (despite the new commit

[fossil-users] EXECUTABLE, and not really being added to updated repo

I've got a collection of files who's apparently only change is the EXECUTABLE bit set, but after a commit, they're still showing up in "f chan"; I retried w/ a --sha1sum switch; still listed as changed (despite the new commit showing up in the "f timel"). touch(1) all the affected files to bump

Re: [fossil-users] Repo Checksum Speedup Idea: flaw in my comment

On Mon, 5 Dec 2016 20:23:50 +0200 Martin Vahi wrote: > As it turns out, I already made a mistake > at the tree based algorithm. > > The old, proposed, flawed version: > > ... > > array_of_nodes_with_wrong_x_node_hash=unique_by_node_ID( > >