The 3.2 tree contains a "default/" component to some of the branches which was intended to reflect the default kernel policy. However, the default policy does not add any source changes above and beyond standard/base. Keeping a clear separation between "sources" and "configuration" will help to clarify how the various linux-yocto mechanisms work and ease the barrier to entry. Enforce a strict policy of branch hierarchy reflecting source changes. In this case, dropping "default/" from all paths would accomplish this.
This change has been made, and you can see it in: http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-dev/ And will be the base of any new trees.
Bruce, can we mark this as RESOLVED?
Yes, this is done in linux-yocto-dev, and will appear in linux-yocto-3.4. This is done. Marking it as such.