Date: Sat, 28 Oct 2006 20:16:47 +0200 From: hans@lambermont.dyndns.org (Hans Lambermont) To: freebsd-ports@freebsd.org Subject: Re: port_history - track port commit message comments Message-ID: <20061028181646.GG19996@leia.lambermont.dyndns.org> In-Reply-To: <20061028002501.32f5b845@it.buh.tecnik93.com> References: <ehs1qk$6pa$1@sea.gmane.org> <cb5206420610270526p56bf0457i8e780b948a392d05@mail.gmail.com> <20061027231646.5b07bd8f@it.buh.tecnik93.com> <cb5206420610271404hbb3ba6an99377535ebe1af98@mail.gmail.com> <20061028002501.32f5b845@it.buh.tecnik93.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ion-Mihai IOnut Tetcu wrote: ... >>>> On 10/27/06, Christopher Boumenot wrote: >>>>> Every time I upgrade a port I am usually left wondering what >>>>> changed. ... > The problem with the OP's work is that some submitters/commiters think > that the CVS commit message should document the _port_ changes while > others think it should also document (or at least provide pointers) to > the changes in the software itself (I fall in the second category). > Since we don't have a standard for this, relaying only on the CVS logs > might drive one into nasty problems. But it is much better than what we have now (nothing) and I think that having a system like what Christopher proposed probably leads to establishing a standard (preferably of the second category :) . If the information is easily available I think it will be used. regards, Hans Lambermont
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061028181646.GG19996>