From 2b55d867035706fc585e29673469a573221dbf90 Mon Sep 17 00:00:00 2001
From: Rob Landley Toybox
-hasn't always taken proper advantage of external contributions.
+ Toybox hasn't always
+taken proper advantage of external contributions.
Lots of people want to help, but their contributions languish out of tree
or in the "pending" directory, awaiting cleanup.Index
+
+
+
+
+
+
Cleaning up the toybox code.
-
In hopes of teaching more people how to do this cleanup work, I've started breaking cleanup changes into smaller chunks and posting explanations of each change to the mailing list. -Below are indexes of each cleanup series. Line/byte totals of completed -series are given for scale, but the point of this work is simplicity, not -size.
+Below are indexes of such cleanup series. Each commit and post are meant to +be read together: each description explains what the corresponding patch +was trying to accomplish. -(Note: mercurial's web viewer doesn't follow renames, so the commit list -links may not show the final version of each file moved from the "pending" +
Line/byte totals of completed series are given for scale, but the point +of this work is simplicity and compactness, not size per se.
+ +(Note: mercurial's web viewer doesn't follow renames, so although each +command name links to a commit list with the bulk of the changes, it may +not include the final version of each file moved from the "pending" directory to its final location. The summaries link the initial and cleaned versions of each file when giving line counts.)
General advice and/or policy:
- -Error messages and internationalization.
+ +The design of toybox page and the coding +style section at the start of the source code walkthrough +don't cover everything. Here are some +links to mailing list messages that cover various programming topics +not directly related to a specific cleanup series:
-(I leave the Why not "bool"? explanation to Linus Torvalds.)
- -Rationale for removing debug code, the interesting bit says:
-+Rule of thumb: other people's debugging printfs are seldom as -useful as your own debugging printfs. Because you know what your output -_means_, and if you can't annotate the code to dump what you need you haven't -read enough of it yet. -
This is an example of cleaning up something that started in a condition most projects would be quite happy with. @@ -75,7 +96,9 @@ description: test suite.
Status: COMPLETE
-I tried to do the uudecode cleanup in smaller stages:
+I tried to do the uudecode cleanup in smaller stages than uuencode:
Status: COMPLETE
+The largest (ongoing) documented cleanup to date, still in progress:
+When ifconfig was submitted, it touched a half-dozen files. I glued it +together into a single self-contained file, which needed a lot of +cleanup. The final version is about 1/3 the size of the original.
+ +This was the first command I started cleaning up with the intent of +describing the process, and especially the first few entries in this +series describe many of the low hanging fruit techniques used to clean +up a codebase.
Status: in progress.
+Status: COMPLETE.