On Sat, Mar 2, 2013 at 9:57 PM, mrafayaleem <notifications@github.com>wrote:


> I will add this to it. However, since I am not very comfortable with git
> right now, can you please point me on how to propagate the new changes to
> this pull request? Should I create a new pull request after I make changes?
> That would mean that someone would have to close this pull request, right?
>

You should not need to create a new pull request.  I think its best to just
add new commits to your master branch (so its easier for reviewers to see
what you've changed from one submit to the next).   Later on, you can
either collapse all the layers of commits into a single commit or the
maintainers can take the whole stack of commits.  But, until then, I think
you should make your changes, commit them, and push them up to github.  See
http://stackoverflow.com/questions/7947322/preferred-github-workflow-for-updating-a-pull-request-after-code-review

For future reference, you should probably create a feature branch (separate
from your master), and make the pull request from that, but its not a big
deal.  (Your master branch will just be tied up with this change until its
completed).