Date: Mon, 1 May 2000 11:19:23 +0200 From: Andreas Klemm <andreas@klemm.gtn.com> To: Kris Kennaway <kris@FreeBSD.org> Cc: Andreas Klemm <andreas@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: ports/net/zebra Makefile ports/net/zebra/files md5 Message-ID: <20000501111923.A30799@titan.klemm.gtn.com> In-Reply-To: <Pine.BSF.4.21.0005010118120.17726-100000@freefall.freebsd.org>; from kris@FreeBSD.org on Mon, May 01, 2000 at 01:19:37AM -0700 References: <200005010702.AAA11563@freefall.freebsd.org> <Pine.BSF.4.21.0005010118120.17726-100000@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 01, 2000 at 01:19:37AM -0700, Kris Kennaway wrote: > On Mon, 1 May 2000, Andreas Klemm wrote: > > > Update zebra to 0.86 > > From its developer: > > Hi, this is Kunihiro. > > [...] > > Is it really necessary to include all this in the commit log? Presumably > it's all in the zebra changelog for anyone who is interested. I thought people would be interested to get detailed information what has changed in zebra. I don't do it for every port, only in this case because zebra is a nice successor for gated and this seems to be the first developer release, where some things have stabilized. But while we are at it... Are there technical issues with long committ messages ? Generally people want informative committ messages. Why not in this case ? Are there some rules of thumb ? -- Andreas Klemm http://people.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD New APSFILTER 542 and songs from our band - http://people.freebsd.org/~andreas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000501111923.A30799>