GitLab | Workflow for contrib projects (#99)

[Amar Takhar (@amar)]

Amar Takhar commented on a discussion: https://gitlab.rtems.org/administration/gitlab/-/issues/99#note_124799


libbsd isn't a patch it's a separate project that we maintain ourselves.

A patch to an upstream is a different story -- we aren't maintaining the software and it's not its own project.  We have 1 libbsd with maintainer(s).

This has been a historical problem in the project with patches piling on and on and the number one concern with doing this is not upstreaming them and finding ways to "keep them around".

As you said we'll cross that bridge if it ever comes to it but at this point we'd do whatever we could to avoid having to maintain a local patch with finding a way to upstream it or avoid requiring it as the only two solutions.

-- 
View it on GitLab: https://gitlab.rtems.org/administration/gitlab/-/issues/99#note_124799
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/20250617/3c6bfb45/attachment.htm>