From owner-freebsd-hackers Sat Jun 29 20:13:04 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA08775 for hackers-outgoing; Sat, 29 Jun 1996 20:13:04 -0700 (PDT) Received: from rocky.mt.sri.com ([206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA08770 for ; Sat, 29 Jun 1996 20:13:01 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id VAA04727; Sat, 29 Jun 1996 21:12:50 -0600 (MDT) Date: Sat, 29 Jun 1996 21:12:50 -0600 (MDT) Message-Id: <199606300312.VAA04727@rocky.mt.sri.com> From: Nate Williams To: Heikki Suonsivu Cc: freebsd-hackers@freebsd.org Subject: Re: Alternate lists for more verbose CVS commit messages? In-Reply-To: <199606292040.XAA19042@cantina.clinet.fi> References: <199606292040.XAA19042@cantina.clinet.fi> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I often would like to know more about problems certain commit might fix, > and see what modifications were committed. Could it be possible to create > alternate commit lists which would receive detailed commit messages ? Sure, sup/CTM/CVSup the CVS tree and anything you find interesting you can check out for yourself. As far as 'finding' out about which problems might be fixed, if they are not obvious or listed in the commit log then you'll have to figure it out for yourself. > Getting a full CVS diff would be helpful, if nothing else. If you have the CVS tree, then you have the diff. Creating yet-another-mailinglist with something like diffs would use up way too much bandwidth IMHO. Nate