Date: Tue, 23 Jan 2007 02:57:26 -0800 From: Luigi Rizzo <rizzo@icir.org> To: developers@freebsd.org Cc: gnome@freebsd.org, ports-developers@freebsd.org, python@freebsd.org Subject: messages to port-developers (Re: The way to fix ports/104560) Message-ID: <20070123025725.A39529@xorpc.icir.org> In-Reply-To: <20070123104738.GA41157@qlovarnika.bg.datamax>; from vd@FreeBSD.org on Tue, Jan 23, 2007 at 12:47:38PM %2B0200 References: <20070123104738.GA41157@qlovarnika.bg.datamax>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070123025725.A39529>