On Thu, 12 Feb 2015 17:59:33 +0100, Warren Young w...@etr-usa.com wrote:
On Feb 12, 2015, at 9:55 AM, j. van den hoff
veedeeh...@googlemail.com wrote:
making the probability threshold user settable instead seems less
convenient since it is just
a statistical measure and it is
On Thu, Feb 12, 2015 at 2:55 PM, Warren Young w...@etr-usa.com wrote:
I would still prefer that Fossil self-tune, however. While it is true
that my formula doesn’t give intuitive p values, it is also true that you
cannot pick sensible d values for a repository without knowing various
On Feb 12, 2015, at 10:55 AM, j. van den hoff veedeeh...@googlemail.com
wrote:
p = 0.1 suggests that I easily will get a collision in my interaction with
fossil while all it tells is that in about 10% of repos of this size there
will
be somewhere a collision
Fair point.
I would still
Andy Bradford amb-fos...@bradfords.org writes:
Thus said Richard Hipp on Wed, 11 Feb 2015 10:21:32 -0500:
https://www.fossil-scm.org/skin2
Please let me know if you see any problems with the look of this
alternative skin.
Looks nice, except it has no background color.
On Thu, 12 Feb 2015 21:17:41 +0100, Ron W ronw.m...@gmail.com wrote:
On Thu, Feb 12, 2015 at 2:55 PM, Warren Young w...@etr-usa.com wrote:
I would still prefer that Fossil self-tune, however. While it is true
that my formula doesn’t give intuitive p values, it is also true that
you
cannot
Hello,
in fossil wiki format link to the other wiki like [OtherWikiName] works.
Markdown link in the form of [OtherWikiName](OtherWikiName) doesn't.
It seems that currently working markdown syntax is
[OtherWikiName](wiki?name=OtherWikiName)
Does it make sense to you to interpret more simple
On 2/12/2015 1:30 PM, j. van den hoff wrote:
it would be good if the user could just do
`fossil set prefix-length 12' thus getting rid of the
collisions and proceed. in short: an option to
customize the length might still be useful.
For small and young projects, a prefix of 10 feels
Great work on the new skin - about time!
On 12 Feb 2015, at 2:21 am, Richard Hipp d...@sqlite.org wrote:
[…] Please let me know if you see any problems with the look of this
alternative skin.
1) In the ‘Timeline’ page, the sub-menu buttons (“Older”, “Search” and
“Unhide”) have no border
Wed, 11 Feb 2015 16:29:21 +0100 j. van den hoff
veedeeh...@googlemail.com:
the box for specifying the max. number of displayed entries is
seriously clipped/not adjusted to textwidth within (see attachment if
this goes through...).
The input size= has been changed to =4 meanwhile. Maybe your
On Wed, Feb 11, 2015 at 5:21 PM, Richard Hipp d...@sqlite.org wrote:
You can now access the Fossil self-hosting repository using the San
Francisco Modern skin at:
https://www.fossil-scm.org/skin2
Please let me know if you see any problems with the look of this
alternative skin.
When
On Thu, Feb 12, 2015 at 9:59 AM, Baruch Burstein bmburst...@gmail.com
wrote:
On Wed, Feb 11, 2015 at 5:21 PM, Richard Hipp d...@sqlite.org wrote:
You can now access the Fossil self-hosting repository using the San
Francisco Modern skin at:
https://www.fossil-scm.org/skin2
Please let
On Thu, Feb 12, 2015 at 1:01 AM, Rich Neswold rich.nesw...@gmail.com
wrote:
IMO, though, I don't like the lines of text that close together, so I'd
add a CSS directive like line-height: 125% to give a little spacing. But
that's just me. Otherwise, it's a nice, contemporary look.
It's not
On Feb 11, 2015, at 7:23 AM, Richard Hipp d...@sqlite.org wrote:
On 2/11/15, j. van den hoff veedeeh...@googlemail.com wrote:
whatever the reason, the netbsd example (a worst case scenario, really)
would suggest to chose 12 instead of 10 as the future default length
to avoid collisions
On Thu, 12 Feb 2015 17:21:50 +0100, Warren Young w...@etr-usa.com wrote:
On Feb 11, 2015, at 7:23 AM, Richard Hipp d...@sqlite.org wrote:
On 2/11/15, j. van den hoff veedeeh...@googlemail.com wrote:
whatever the reason, the netbsd example (a worst case scenario, really)
would suggest to
On Feb 12, 2015, at 9:55 AM, j. van den hoff veedeeh...@googlemail.com
wrote:
making the probability threshold user settable instead seems less convenient
since it is just
a statistical measure and it is counterintuitive in the sense that it tells
you something about
chance of
On Feb 12, 2015, at 9:59 AM, Warren Young w...@etr-usa.com wrote:
Any value for d 40 gives p 1.0. :)
Ooops. I mean p 0.
And yes, I realize that p never goes to 0, but since 40 digits puts the chance
of collision into “heat death of the universe” territory, it’s close enough to
0 for my
On Feb 12, 2015, at 9:21 AM, Warren Young w...@etr-usa.com wrote:
d = log2(n^2 / 2p) / 4
In C:
double n = num_artifacts;
double p = acceptable_probability_of_collision;
assert(p 0.002);
int d = ceil(log2((n * n) / (2 * p)) / 4.0);
n needs to be a double because squaring 5 and
17 matches
Mail list logo
