On Mon, Apr 07, 2014 at 10:04:07AM -0700, Brian Miles wrote:
> Perhaps you could add something to this effect once the pull request
> is merged?

You don't need to wait until a PR is merged before collaborating.  You
can always checkout a local copy of the source branch (here
selimnairb/master):

  $ cd ~/src/bc
  $ git remote add selimnairb https://github.com/selimnairb/bc.git
  $ git fetch selimnairb
  $ git checkout -b multiprocessing selimnairb/master

then add your tweak commit, and make a pull request against
selimnairb/master.  When Brian merges the PR into his repository, this
PR will be updated to point at his new branch.  In ASCII art, here's
the original pull request into origin/master (at B) from
selimnairb/master (at A):

  -o---o---B  origin/master
    \
     o---A  selimnairb/master

Here's the update pull request into selimnairb/master (at A) from
multiprocessing (at C):

  -o---o---B  origin/master
    \
     o---A  selimnairb/master
          \
           C  khinsen/multiprocessing

Brian accepts the pull request:

  -o---o---B  origin/master
    \
     o---A---D  selimnairb/master
          \ /
           C  khinsen/master

After which this PR will bring D (the new selimnairb/master tip) into
origin/master (still at B).  When Greg (or someone) merges this PR
into master, we'll have:

  -o---o---B---E  origin/master
    \         /
     o---A---D  selimnairb/master
          \ /
           C  khinsen/master