Cleanup compiler warnings on liblustre - patch by nic@cray.com

b=11175
r=adilger
r=green
r=scjody

r=adilger

Add comment to ensure people keep branch list sorted.

Teach lustrecvs and buildcvs about b_release_1_4_7-test branch. sigh.

build-core's HEAD is going to diverge for 1.6.0, so "capture" build-core's
current state in a branch mainly for b1_4.
Note that b_release_1_4_6-patchless is not really a release branch and thus
tracks b1_4.
Also, v1_2_8 and v1_4_0 pre-existed this build system so which branch to
check out for them is actually quite moot.  Let's just keep them tracking
b1_4.

Landing LNET (b1_4_newconfig)

- lustrecvs already has a regexp for all v* tags
- change buildcvs regexp to include lnet for v1.4.5.10+

on b1_4 now.

Add support for b_lnet branch of the ./build tree to cleanly
seperate the changes related to LNET reorg that is going on on the
b1_4_newconfig branch(s).

(Consulted with Jacob and Andreas on this change)

Check out the tagged version of the lustre-build scripts, so we are sure
to use the same ones as when the packages were originally built.

 - print a summary of failed updates/checkouts at the end
 - also return an error status in this case

Handle "./lustrecvs -r foo" instead of choking.

complain if more than one argument was passed, so that people who do ./lustrecvs co -r foo get an error as soon as practical

 - set LC_COLLATE=C otherwise [a-z] and [A-Z] don't work how we expect
   them to

 * get rid of LC_{DARWIN,LINUX}_SUPPORTED in favor of more general
   LC_TARGET_SUPPORTED
 * fix some typos and spacings

own buildcvs scriptlet.