From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from metis.ext.pengutronix.de ([2001:6f8:1178:4:290:27ff:fe1d:cc33]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1WkCTF-0004Id-RK for barebox@lists.infradead.org; Tue, 13 May 2014 13:10:15 +0000 From: Juergen Borleis Date: Tue, 13 May 2014 15:09:09 +0200 References: <1399969739-10355-1-git-send-email-holgerschurig@gmail.com> <20140513162340.c2689ed174c2ad441edceab1@gmail.com> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Message-Id: <201405131509.09847.jbe@pengutronix.de> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: "barebox" Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: [PATCH 08/19] commands: move CMD_MIPS_CPUINFO to commands/Kconfig To: barebox@lists.infradead.org On Tuesday 13 May 2014 14:43:38 Holger Schurig wrote: > If it would be to me, I'd in long-term kill the doxygen. Or have the > doxygen only describe the internal API for barebox programmers. > Currently it mixes internal API and end-user documention, not so nice. The historical goal was to keep all the documentation and the corresponding = code close to each other. The API documentation of doxygen is mostly useless. But to have the descrip= tion = of the intention of the code close to the code was my idea, to make = programmers also change the documentation when they change the code near by= . = But it doesn't work. Programmers are not interested in writing documentatio= n. jbe -- = Pengutronix e.K. =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0| Juergen Borleis =A0 =A0 =A0 =A0 =A0 =A0 | Linux Solutions for Science and Industry =A0 =A0 =A0| http://www.pengutroni= x.de/ | _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox