From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <5d375e920709100139q174b5e72gce2024bf9a26358e@mail.gmail.com> Date: Mon, 10 Sep 2007 10:39:03 +0200 From: Uriel To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] venti woes with brand new install In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46e290f8.0d375e0a.1d4b.fffff33d@mx.google.com> <01405c4bddab6004f67d7e604d29ba72@quanstro.net> <46e3e080.1f205e0a.7670.53fc@mx.google.com> Topicbox-Message-UUID: bda21140-ead2-11e9-9d60-3106f5b1d025 I created plan9changes (and try to keep it running), and its value is limited because only a very very small percentage of changes are submitted though patch(1). There have been efforts in the past for someone to manually annotate automatically generated diffs in a 'post-facto' way, nobody lasted long doing it, which is unsurprising given that this involved the person writing the changelog entries having to guess the reasons for the changes (painful and errorprone) and often having to check with whoever made the change (tedious, slow and rather neutralizing the whole point of having a changelog). Why this approach was considered a good idea rather than having the author of the change write a changelog entry at the same time the change is made/committed-to-sources is something I have never understood. uriel On 9/10/07, SHRIZZA wrote: > > I'm wondering how I will know when I can get back to using the > > sources venti, a changelog of some-sort would be welcomed to see > > when a specific change has been made. For example this time it > > would be nice to know when I need not be worried about being able > > to boot with venti if I recompile the kernel. > > http://groups.google.com/group/plan9changes >