On Sat, Feb 17, 2024 at 10:35 AM Sebastian Huber <sebastian.hu...@embedded-brains.de> wrote: > > On 17.02.24 18:11, Joel Sherrill wrote: > > > > On Wed, Feb 14, 2024, 9:54 PM zack leung <zakthertems...@gmail.com > > <mailto:zakthertems...@gmail.com>> wrote: > > > > > This file is generated from something in rtems-central. This was at > > the > > > top of the file: > > > > > > * This file is part of the RTEMS quality process and was > > automatically > > > * generated. If you find something that needs to be fixed or > > > * worded better please post a report or patch to an RTEMS mailing > > list > > > > No, problem. I can fix this before I check in the patch. > > > > re: this do you need me to change it to something? > > > > > > I'm hoping Sebastian has some guidance for you on what to edit for this > > and how to propagate it dull. > > Just for this patch it would be a bit of on overkill. I will take care > of this when I check in the patch. >
Is there a simple way we can add some checks for modification of generated files into a commit hook? And then, point to a documentation that helps explain where to go for more guidance depending on the code generation source? I would use this for all rtems-central generated stuff, and also for 3rd party sources where there's an active upstream. I can add such a plan to follow #4663 Third-Party Sources Manifest Gedare _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
