On Tue, May 25, 2021 at 10:22 AM Sebastien Lorquet <sebast...@lorquet.fr> wrote: > > it will be easier next time.
Yes the workflow of git in general is a lot of steps to do a simple thing. If you'd like to, you can still send patches to the mailing list. Just please remember to name the file with ".txt" extension or the mailing list will drop it. If you send a patch rather than a PR, someone will convert it into a PR on GitHub, because we don't commit directly to the repository anymore. It's part of taking the burden off of Greg and allowing the community to split the work. You can keep a fork of NuttX in your GitHub; then you won't need to fork it again. You just need to remember to create a branch each time you want to make a PR, because if you create the changes on master then you'll end up having to delete your fork and then make a new fork. Also it's not possible to have multiple forks of the same repo in one GitHub account. Note that if you want to keep your fork in GitHub, it will get out-of-date with NuttX's repo, but you can bring it up-to-date with something like: Add the official repo as a remote called "upstream": $ git remote add upstream https://github.com/apache/incubator-nuttx.git Fetch new commits from there: $ git fetch upstream Make sure you're on your master branch: $ git checkout master Rebase your master branch to upstream/master. Assuming you haven't made any commits on your master branch, this shouldn't have to do anything: $ git rebase upstream/master Then push it back to GitHub: $ git push origin A lot of steps. :-) (But much faster than deleting the fork and forking again.) This won't sync your fork with things like new tags that are created upstream. There are other git incantations for that, which I can't remember right now. > Does any of the 21 queued test that I see waiting in github enable this > driver? I don't know the answer to that, but... > Because if they dont (which I suspect, hence this typo) these tests are > useless. ...we have had discussions about trying to make the pre-checks smarter about what they check in the future. Thanks again, Nathan
