From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert Schwebel Date: Fri, 7 Mar 2003 09:34:07 +0100 Subject: [U-Boot-Users] Enforcement of coding standards In-Reply-To: <20030307081203.18FE8C6E0C@atlas.denx.de> References: <20030307062951.GD16290@pengutronix.de> <20030307081203.18FE8C6E0C@atlas.denx.de> Message-ID: <20030307083407.GN16290@pengutronix.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Fri, Mar 07, 2003 at 09:11:58AM +0100, Wolfgang Denk wrote: > Obviously, I am interested in keeping these diff's as small as > possible. Running "cb" or "indent" over a source file makes a diff > against earlier versions basicly useless. Understandable - would it help if we had something like a stable and unstable branch? I mean, the problem is that for the short time you are perfectly right with your arguments. But long term some parts of the code definitely have to be cleaned up or everybody will be lost. For the moment I don't really care about the huge rest of the code; the things I'm working on are currently mostly PXA related and I consider the PXA port still being code under construction. Perhaps some kind of a release plan would be helpful for the project, now that the code seems to work for several people. One could make checklists for a release, something like board compiles tested maintainer tested-by ... foo x x Fridolin Tux Erich Tux ... This would mean to push the QA from CVS to release/prerelease level. Robert -- Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Braunschweiger Str. 79, 31134 Hildesheim, Germany Handelsregister: Amtsgericht Hildesheim, HRA 2686 Phone: +49-5121-28619-0 | Fax: +49-5121-28619-4