Central | Various updates (!2)

[Gedare Bloom (@gedare)]

Merge request https://gitlab.rtems.org/rtems/prequal/rtems-central/-/merge_requests/2 was reviewed by Gedare Bloom

--
  
Gedare Bloom commented on a discussion on .gitmodules: https://gitlab.rtems.org/rtems/prequal/rtems-central/-/merge_requests/2#note_112086

 >  	path = modules/rtems
 > -	url = git://git.rtems.org/sebh/rtems.git
 > +	url = https://gitlab.rtems.org/sebhub/rtems.git

I think this MR has exposed an important point that the workflow in `rtems-central` has a backward dependency by relying on a personal repo/fork of `rtems.git`. Although it means currently rtems-central is broken, the proposed fix here means continuing to hide this backward dependency. What would it take to be able to use the actual `rtems.git` in the workflow? 

What is in your developer version of `rtems.git` to enable this workflow to work, that doesn't exist in the upstream `rtems.git`?

I don't know what it means "I have to carry about 28 commits around". What is selecting the branch on the rtems.git submodule to do the regeneration and generate the patch sets?

I may be willing to accept the maintenance updates, if I can see an Issue and a plan for how to resolve this backward dependency.


-- 
View it on GitLab: https://gitlab.rtems.org/rtems/prequal/rtems-central/-/merge_requests/2
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/20240914/f80341e1/attachment-0001.htm>