RTEMS | cpukit/rtems: Closes rtems/programs/gsoc#9 (!443)

[Gedare Bloom (@gedare)]

Gedare Bloom commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/443#note_120604


I see, ok in that case you might want to close the original MR that used your `main` branch on your fork, and switch to a different branch / re-open this MR. I think that you can also unset your own `Protected` branch setting on your fork, however, I think it is better if you just use branches for your MR.

Regarding working with rtems-central, the documentation should be a little help, but yes it may not spell out how to create the MR from it. I think the process is supposed to be to use `git-commit` inside of the submodule in `modules/rtems` and then use `git-format-patch` or similar to export the commit, and then you can apply it to a branch you checked out elsewhere. Alternatively, you can add your forked rtems.git as a `remote` within your `modules/rtems` and directly create git branches and push from there, just as if you had checked out `rtems.git`

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/443#note_120604
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20250305/0b9085f3/attachment-0001.htm>