Page History

...

The generated patch set should be sent to dev@nuttx.apache.org. To make sure that your patch email is noticed, please start the subject line with [PATCH] and a brief description. It is best to send the patch as an attachment with a .txt extension, as that ensures it gets the correct MIME type and isn't blocked by the mailing list's spam filter.

Your patch will be reviewed by the community and incorporated when everything is okay. If a change is required, address that and provide another patch.

Getting to this point your patch has been accepted and pushed to the main repository. Thank you for your contribution.

Now, you need to re-synch your local clone. It's important to note that committers can do some minors changes in your behalf, so always pull the latest changes.
If you were working on a branch, just delete the branch and pull master. You can do this with the following GIT commands.

git checkout master # If you are not already in master

git branch -D <branch_name>

git pull origin master

If you were working on master, reset the HEAD back to where origin was and pull master.

REVISIT: Anything better then the cruel reset --hard?

git reset --hard origin/master

git pull origin master

Generating a GitHub Pull-Request from a Fork

...