1.1 --- a/__brch__Dev_Univ	Sun Sep 15 19:07:01 2013 -0700
     1.2 +++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.3 @@ -1,28 +0,0 @@
     1.4 -This branch is for developing the multi-language capability in VMS.  The idea is to define langlets, whose constructs can be freely mixed together inside application code.  No need to separate into distinct modules.  A single function can use constructs from all the different langlets together inside itself.
     1.5 -
     1.6 -
     1.7 -========  Background on branch naming  =========
     1.8 -
     1.9 -There are two kinds of branchs: ones used to develop features, and ones tuned to particular hardware.  A given HW branch may combine features from several feature-branches, picking and choosing among them.
    1.10 -
    1.11 -After Feb 2012, branches are named by the scheme:
    1.12 -
    1.13 -feat__<feat_descr>__<HW_feat_dev_on>
    1.14 -
    1.15 -HW__<desc_of_HW_brch_tuned_for>
    1.16 -
    1.17 -where <HW_feat_dev_on> and <desc_of_HW_brch_tuned_for> follow the pattern:
    1.18 -
    1.19 -<num_socket> x <num_cores>_<Manuf>_<special_features>
    1.20 -
    1.21 -Examples:
    1.22 -
    1.23 -feat__exp_array_malloc
    1.24 -
    1.25 -feat__rand_backoff__4x10_Intel_WestmereEx
    1.26 -
    1.27 -HW__1x4_Intel_SandyBridge
    1.28 -
    1.29 -HW__4x10_Intel_WestmereEx
    1.30 -
    1.31 -HW__1x4_AMD_mobile

     2.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     2.2 +++ b/__brch__ML_lib	Thu Sep 19 17:57:38 2013 -0700
     2.3 @@ -0,0 +1,28 @@
     2.4 +This branch is for developing the multi-language capability in VMS.  The idea is to define langlets, whose constructs can be freely mixed together inside application code.  No need to separate into distinct modules.  A single function can use constructs from all the different langlets together inside itself.
     2.5 +
     2.6 +
     2.7 +========  Background on branch naming  =========
     2.8 +
     2.9 +There are two kinds of branchs: ones used to develop features, and ones tuned to particular hardware.  A given HW branch may combine features from several feature-branches, picking and choosing among them.
    2.10 +
    2.11 +After Feb 2012, branches are named by the scheme:
    2.12 +
    2.13 +feat__<feat_descr>__<HW_feat_dev_on>
    2.14 +
    2.15 +HW__<desc_of_HW_brch_tuned_for>
    2.16 +
    2.17 +where <HW_feat_dev_on> and <desc_of_HW_brch_tuned_for> follow the pattern:
    2.18 +
    2.19 +<num_socket> x <num_cores>_<Manuf>_<special_features>
    2.20 +
    2.21 +Examples:
    2.22 +
    2.23 +feat__exp_array_malloc
    2.24 +
    2.25 +feat__rand_backoff__4x10_Intel_WestmereEx
    2.26 +
    2.27 +HW__1x4_Intel_SandyBridge
    2.28 +
    2.29 +HW__4x10_Intel_WestmereEx
    2.30 +
    2.31 +HW__1x4_AMD_mobile

     3.1 Binary file libpr__ML_lib__mc_sharedmem.so has changed