On Thu, Apr 23, 2026 at 6:28 AM David Hildenbrand (Arm) <[email protected]> wrote: > > On 4/22/26 21:08, [email protected] wrote: > > (Resending to correct David's email address. Apologies for the noise!) > > > > Heh, no worries, I didn't even notice. > > As long as you CC one of the mailing lists I'm subscribed to, even mails to my > old RH address will still hit my inbox. > > > On 4/22/26 18:04, David Hildenbrand (Arm) wrote: > >> On 4/21/26 20:30, [email protected] wrote: > >>> From: Pratyush Mallick <[email protected]> > >>> > >>> The current .gitignore hardcodes each generated test binary by name, > >>> requiring updates every time a new test is added. > >>> > >>> Switch to the patten-matching approach similar to KVM:selftests. > >>> Ignore everything by default and then allow source extensions (.c, .h, > >>> .sh) > >>> and tracked non-source files. > >> That looks pretty nice. Any reason for the RFC? (iow, are you unsure about > >> some > >> side-effects?) > > > > Exactly that. I verified that the build works fine, however I sent it > > as an RFC just to be cautious. I wanted to get some feedback in case this > > might introduce some unwanted behavior that I'm not aware of. :) > > After taking a peek at the KVM one, I think what you propose makes perfect > sense. > > I do wonder, whether we want to make our lives easier and rename > "local_config.h" to something like "local_config.h_gen", so we don't need the > "re-ignore" part.
There's also the *.mod.c part, but I am not sure why that is needed as the current .gitignore doesn't have anything with .mod.c in it.
