Changes between Version 30 and Version 31 of StartModMaint


Ignore:
Timestamp:
Dec 21, 2013, 2:34:44 PM (9 years ago)
Author:
Beman Dawes
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • StartModMaint

    v30 v31  
    3434}}}
    3535
     36The {{{git submodule update}}} switches submodules back to the detached state if the submodule is already at the commit specified by the super-project for that submodule. Otherwise the submodule stays at the commit (and branch) it is already on.
     37
     38To get more information about submodules, do:
     39
     40{{{
     41cd modular-boost
     42git submodule summary
     43}}}
     44
    3645If for some reason you wanted to test against the current head of {{{master}}} for all libraries, disregarding the super-project state, the {{{git submodule update}}} command would be changed to:
    3746
    … …  
    206215Large, complex libraries, particularly those with multiple developers working in parallel, need to use a release procedure that scales up better than the lightweight procedure. The Git Flow approach is recommended. Find out more at [wiki:StartModWorkflow Modular Boost Library Workflow Overview] and be sure to study the examples given in [http://nvie.com/posts/a-successful-git-branching-model/ Vincent Driessen's original blog posting].
    207216
     217== Acknowledgements ==
     218
     219Beman Dawes created and maintains this page. The content has been revised many times based on comments and list postings from Andrey Semashev, John Maddock, Daniel James, Michael Cox, Pete Dimov, Edward Diener, Bjørn Roald, Klaim - Joël Lamotte, Peter A. Bigot, and others.
     220
     221
     222