From mint-bounce@lists.fishpool.fi Tue Sep 28 17:47:31 2010 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:x-priority:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=qmQf/4jazBZ5Pe8olxW2ZVAzkTyz6qbkuBKdC3rvLmc=; b=jGvHS39ZzZs2o7svx4oLlF63/y9JXTOtJg1dY6rXHtaZ+sNC4uRL/uko8TU/RHBMH4 xAqPkVreZSrW8KNUnDIgcGOYhIZYcr8kBACKgImGeCQ6LG8Hyv4ULudh9tQHKYmMMTSQ p03fUDXkc/6Ag5zfubSvcLkQ+UXMxQVBE3oI0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:x-priority:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; b=BaaiKpgiXvZrPOmp31E4kau4Gp4sMP4jvXEjmU1ijKBhoysS7S4wfoHApCZ750OHjN GvF4HfqoLXPWEFNXkIqtj6DX2UBUTPlPO+YfrFkUtsvVGAolNUncjp5sVds4I4wHwdKO 4D3skXSNU80VI7Zs/kQ41k4re6mrLlKdYl/6U= Subject: Re: [MiNT] cookie jar Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Peter Persson X-Priority: 3 In-Reply-To: <0034de59.01c732623998@smtp.freeola.net> Date: Tue, 28 Sep 2010 23:39:46 +0200 Cc: Message-Id: <6C467248-1F35-40E7-9E63-8602BCB12235@gmail.com> References: <4CA24BAD.5060000@online.no> <0034de59.01c732623998@smtp.freeola.net> To: Peter Slegg X-Mailer: Apple Mail (2.1081) X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: pep.fishmoose@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id o8SLlVMu009526 28 sep 2010 kl. 22.18 skrev Peter Slegg: >> Yes, debugging can be tedious. Now imagine how to debug this without >> being able to reproduce the problem! That's why it's so important (and >> valuable to the developers) to find out how to reproduce a bug. >> > Yes, well I have been a developer since the early 80's. The usual > suspect is the last thing that changed caused the problem. Man, are you kidding? The last thing that changed could just as well trigger bugs in some other application, bugs which would never manifest themselves earlier. I won't brag about my previous experience, because I see no reason to have a (bad word for a certain male organ)-measuring contest over matters such as this one. Having said that, it could of course be caused by a bug in the kernel too. But refusing to do your own part because of pride is nothing short of silly, if not rude. -- PeP