Hacking Boost via Git

This is not a proposal to switch main source control for boost away from subversion to git. In the meantime, this evolving document intends to

• provide a demonstration of the system and a “try it out” process for the curious
• propose a superior alternative to current sandbox/vault practice
• establish best practices for those who are already hacking boost via git
• serve as a reference point for discussion and experimentation

Highly recommended reading:

Thanks to the folks on freenode’s #git:

• Git from the bottom up (See also the links at the end of this document).
• Git for Computer Scientists
• Git home page

YouTube:

• Linus Torvalds on Git the now famous Google Tech Talk. A must-watch.
• Contributing with Git Johannes Schindelin’s Google Tech Talk. Good for beginners.

IRC

#alt.boost on freenode.

Contents

• Getting started
  • Register and make a clone on gitorious
  • Clone your clone to your local machine
  • Add a remote for svn
• Do some development
  • Make a local “feature” branch
  • Hack hack
  • Redo a bad commit
  • Rebase
  • Push out our code
  • Lather, rinse, repeat
• Committing back to subversion
• SVN Command equivalents
  • svn cat
  • svn revert
• Various HOWTOS
  • Diff trunk and release
  • Track a particular branch
  • Get files from another branch
• How this was all set up

About this documentation

This documentation is written in reStructuredText and assembled by Sphinx. You can get the source from the boost-git-docs branch of the git repository at git://sodium.resophonic.com/boost_cookbook.

Why alt dot boost?

Because this neither official boost nor currently proposed. It is a separate effort that proceeds independently of upstream boost.