Changes between Version 6 and Version 7 of ModCvtFAQ


Ignore:
Timestamp:
Dec 24, 2012, 4:04:54 PM (10 years ago)
Author:
Beman Dawes
Comment:

Add push fixes question

Legend:

Unmodified
Added
Removed
Modified
  • ModCvtFAQ

    v6 v7  
    1 = Modular Boost Conversion Frequently Asked Questions =
     1= Modular Boost Frequently Asked Questions =
    22
    3 **What is the role, if any, of Ryppl and CMake in the Boost modularisation plan?**
     3== Conversion to Git and modular Boost ==
     4
     5**What is the role, if any, of Ryppl and CMake in the Boost modularization plan?**
    46
    57 None. Modularization + the move to Git is a big enough change to be done separately and to stand on its own merits.
     
    1315 Not automatically. Automatic dependency resolution is planned for the future, but not as a part of the conversion to Git and modular Boost.**
    1416
     17== General Questions ==
     18
    1519**How do I get write access to my library at {{{github.com/boost-lib}}}?**
    1620
    1721 See [ModAdmin Administrative Privileges for public library repositories].
     22
     23**How do I submit fixes to a Boost library owned by someone else?**
     24
     25 The Git community has a usual way of submitting changes upstream. See [https://help.github.com/articles/fork-a-repo GitHub's] description of the process. [http://stackoverflow.com/questions/2199144/github-git-how-to-submit-changes-to-an-upstream-repo Stackoverflow] also covers the topic. This [http://www.youtube.com/watch?v=75_UrC2unv4 video] shows how !GitHub manages interactions between the submitter and the library owner.