GitLab | Workflow for contrib projects (#99)

[Christian Mauderer (@c-mauderer)]

Christian Mauderer commented on a discussion: https://gitlab.rtems.org/administration/gitlab/-/issues/99#note_124695


What about changes that are not accepted upstream but that everyone here agrees should be used? So basically the cases where a mirror becomes a fork where we still want to track upstream branches in `main` but create for example a `rtems-main` branch or something similar?

Currently LibBSD has a different development model due to it's history (I think FreeBSD didn't use git during the first versions). But it could have been an alternative development model to keep all our changes in branches instead of the script that copies between the FreeBSD repo and the LibBSD.

Should repos have some kind of tag or use a different namespace depending on that?

-- 
View it on GitLab: https://gitlab.rtems.org/administration/gitlab/-/issues/99#note_124695
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/20250616/fb305d33/attachment.htm>