From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <3CAA3EEA.D844E7AB@mvista.com> Date: Tue, 02 Apr 2002 15:29:46 -0800 From: Frank Rowand Reply-To: frowand@mvista.com MIME-Version: 1.0 To: andrew may Cc: Matt Porter , Eugene Surovegin , linuxppc-embedded@lists.linuxppc.org Subject: Re: Status of 440GP port References: <5.1.0.14.2.20020402113518.02aa3800@pop.prodigy.net> <20020402141845.A12269@home.com> <20020402134109.A5189@ecam.san.rr.com> <20020402222147.GE20767@beef.az.mvista.com> <20020402145400.B5189@ecam.san.rr.com> Content-Type: text/plain; charset=us-ascii Sender: owner-linuxppc-embedded@lists.linuxppc.org List-Id: andrew may wrote: > < taken totally out of context > > I would expect a development tree to contain non-working and non-tested > stuff. It becomes very help full to see things that get tried but don't > work in the history of a file. It makes a lot more sense to use the version > history to document quirks in hardware than to start putting comments in the > source on what does and doesn't work. The version history does not seem to me a useful place to document quirks in hardware. The history is usually full of so much trivia that it is hard to search. The history also usually doesn't include much in the way of useful information. It seems to me that either the source, or the Documentation directory is a good place to document quirks in hardware. -Frank -- Frank Rowand MontaVista Software, Inc ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/