On Mon, Jan 01, 2001 at 04:01:17PM -0800, Mr.Bad wrote:
> ...and then puts the data in a database and then somebody routes the
> bug reports to the developer most likely to understand/fix the problem
> and...
We tried it - twice (with the sourceforge bug-tracker, and with
Bugzilla) and neither wo
> "IC" == Ian Clarke <[EMAIL PROTECTED]> writes:
IC> Indeed, or perhaps a form on the website which asked the user
IC> for this information (since I bet almost nobody reads the
IC> README).
...and then puts the data in a database and then somebody routes the
bug reports to the de
On Mon, Jan 01, 2001 at 08:29:56PM +, maynard wrote:
> I think it would be a good idea to add a list of desired info for bug
> reports to the README file (at the moment it just says "send a mail to
> <[EMAIL PROTECTED]>"). Something along the lines of:
Indeed, or perhaps a form on the website
>
> PS. I wish all bug reports were this well thought-out.
>
I think it would be a good idea to add a list of desired info for bug
reports to the README file (at the moment it just says "send a mail to
<[EMAIL PROTECTED]>"). Something along the lines of:
Please give us as much detail as you
On 31 Dec 2000, Steven Hazel wrote:
> Speaking of problems with 0.3.6, is anyone else finding that inserts
> with HTL=1 don't work? Everything seems to go fine from the client's
> point of view, but the node gives a null pointer exception, and the
> key doesn't end up in the data store.
Yes. I
Speaking of problems with 0.3.6, is anyone else finding that inserts
with HTL=1 don't work? Everything seems to go fine from the client's
point of view, but the node gives a null pointer exception, and the
key doesn't end up in the data store.
-S
__
Ian,
I had a similar problem, with two reinstalls of the freenet software
.3.6 on windows, closing the console window forcibly seemed to work fine
and cause no ill after effects that I have been able to determine.
Cheers/Dale
On Sun, Dec 31, 2000 at 01:47:19PM -0800, Ian Clarke wrote:
> H,
H, this is the same problem that I experienced with one of the
earlier versions of the 0.3.6 Windows release. I am not sure if
Sebastian is able to fix this, but if anyone else thinks that they can
address the problem and provide a fixed release I will upload it.
Cheers,
Ian.
PS. I wish al
