Even if you know C, the reasons and purpose of a change are very often non-obvious. Specially if you are not familiar with the code being changed and all you want to know is if whatever bug was bothering you is supposedly fixed or not (so you can test it and provide due feedback).
uriel On 9/9/07, John Soros <[EMAIL PROTECTED]> wrote: > True, but there are no comments at all, so I can't really know what the > changes fix. > I'm thinking, as i'm not a big C hacker, that a completely different change > might be made to fix the problem, and the change i'm waiting for would then > never appear. > Oh well, I guess I'm expecting a lot: "comments", but at the same time, > without those how should we know what's happening and why? > > oh well, i guess the answer to this would be "learn C", and btw that is what > i'm doing. > > Regards > John > > > On Sun, 9 Sep 2007 08:05:06 -0400 > erik quanstrom <[EMAIL PROTECTED]> wrote: > > > you can use history(1) on sources. > > > > cpu% 9fs sources > > cpu% cd /n/sources/plan9/sys/src/cmd/venti/srv > > cpu% history ifile.c > > Sep 8 23:03:56 EDT 2007 ifile.c 2592 [geoff] > > Sep 8 23:03:56 EDT 2007 > > /n/sourcesdump/2007/0909/plan9/sys/src/cmd/venti/srv/ifile.c 2592 [geoff] > > Apr 25 17:03:46 EDT 2007 > > /n/sourcesdump/2007/0908/plan9/sys/src/cmd/venti/srv/ifile.c 2327 [geoff] > > > > - erik > > > > > Hi, again me. > > > 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. Thanks for the help, the new kernel with modified > > > venti still works fine. > > > Cheers John > > >
