From owner-freebsd-gnome@FreeBSD.ORG Tue Jan 23 11:17:17 2007 Return-Path: X-Original-To: gnome@freebsd.org Delivered-To: freebsd-gnome@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EF2B616A401; Tue, 23 Jan 2007 11:17:17 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.freebsd.org (Postfix) with ESMTP id C95D113C428; Tue, 23 Jan 2007 11:17:17 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.11/8.13.6) with ESMTP id l0NAvQdj039617; Tue, 23 Jan 2007 02:57:26 -0800 (PST) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.11/8.12.3/Submit) id l0NAvQ7i039616; Tue, 23 Jan 2007 02:57:26 -0800 (PST) (envelope-from rizzo) Date: Tue, 23 Jan 2007 02:57:26 -0800 From: Luigi Rizzo To: developers@freebsd.org Message-ID: <20070123025725.A39529@xorpc.icir.org> References: <20070123104738.GA41157@qlovarnika.bg.datamax> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20070123104738.GA41157@qlovarnika.bg.datamax>; from vd@FreeBSD.org on Tue, Jan 23, 2007 at 12:47:38PM +0200 Cc: gnome@freebsd.org, ports-developers@freebsd.org, python@freebsd.org Subject: messages to port-developers (Re: The way to fix ports/104560) X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jan 2007 11:17:18 -0000 Taking this message as chance to make a comment that i wanted to make for a long time: On Tue, Jan 23, 2007 at 12:47:38PM +0200, Vasil Dimov wrote: > Hi, > > Please take a look at ports/104560 (and also ports/105853 and > ports/106120) and come to a consensus what is the right way to fix this > issue. it happens all the time (not only here i am afraid) that messages related to bug reports are extremely cryptic as the ones above. May i suggest that either in the subject line or at least in the body one puts a human-readable description (e.g. "fixes for memory leak on sysutils/memcheck") rather than a machine-language one ("fix ports/104560") of what the mail is about ? A full URL in the body of the message would also be great. Especially on a global list such as port-developers, it is very useful that one can quickly identify things he is interested in, and filter out the rest thanks luigi