> I don't know where you found that, but my exported node reference with the
> today's snapshot has a version line of:
>
> version=Fred,0.4,1.45,454
Why export noderefs?
~/freenet/lib$ java -jar freenet.jar -v
Fred version 0.4, protocol version 1.45 (build 454, last good build 454)
--
Nevermind, my bad. I messed up exporting myown.ref.
- Original Message -
From: "SiliconZealot" <siliconzea...@attbi.com>
To:
Sent: Monday, January 21, 2002 6:36 PM
Subject: Re: [freenet-devl] build 454 (mandatory): fixed key collisions,
non-caching of DataReplys
&
-devl] build 454 (mandatory): fixed key collisions,
non-caching of DataReplys
> I have checked in several fixes since Friday. Yesterday I checked in
> build 453, which was a mandatory upgrade, and fixed the spurious key
> collisions while inserting. Unfortunately it also introduced a bug tha
d 454 (mandatory): fixed key collisions,
non-caching of DataReplys
> I have checked in several fixes since Friday. Yesterday I checked in
> build 453, which was a mandatory upgrade, and fixed the spurious key
> collisions while inserting. Unfortunately it also introduced a bug that
> s
At 06:36 PM 01/21/2002 -0500, SiliconZealot wrote:
>Um, I think you forgot to increment the build number to 454.
>The lastest snapshot build (21-Jan-2002 15:10) is still numbered 453.
>SiliconZealot
I don't know where you found that, but my exported node reference with the
today's snapshot has
I have checked in several fixes since Friday. Yesterday I checked in
build 453, which was a mandatory upgrade, and fixed the spurious key
collisions while inserting. Unfortunately it also introduced a bug that
stopped the node from caching any DataReplys. So today, build 454 fixes
that bug and
On Mon, Jan 21, 2002 at 04:47:11PM -0500, Tavin Cole wrote:
> I have checked in several fixes since Friday. Yesterday I checked in
> build 453, which was a mandatory upgrade, and fixed the spurious key
> collisions while inserting. Unfortunately it also introduced a bug that
> stopped the node
