On Fri, 2022-03-04 at 00:17 +0100, Miguel Ojeda wrote: > On Thu, Mar 3, 2022 at 11:44 PM Finn Thain <fthain@xxxxxxxxxxxxxx> wrote: > > > > Others might argue that they should always be changed from, > > > > /* > > * this style > > * of multiline comment > > */ > > > > to > > > > /* this style > > * of multiline comment > > */ > > In general, for things that the coding style guide talks about, we > should follow them, even if some subsystems do not (they can always > override in their folder if they really, really want it). So, here for > instance, the first one should be used. It's up to individual maintainers to each decide on what might be considered unnecessary churn for the subsystems they control. One argument is that churn leads to difficulty in backporting fixes to older 'stable' versions. I think the churn argument is overstated.
