Mathieu Barbin

> The (auto)squash step will simply eliminate the fixup commits (aka. merge them into the previous commit). See `man git-rebase`. Thanks a lot for teaching me about `git rebase --autosquash`...

> @mbarbin if you're happy with my proposed changes, I can begin the finalisation. This looks good to me. Thank you for the changes!

Thank you! I don't want to be needlessly difficult, I'm not sure what to think. > (I said the behavior was at least partially intended because we simply did not...

I'll be using `1.07` for now - no time pressure from me. Thanks a lot!

Hello! I wanted to update this ticket with some new information. A few months ago I witnessed a few projects move to a (new?) SPDX convention with [short headers](https://spdx.dev/learn/handling-license-info/). I've...

I'll rephrase here something that came up in the linked issue that may be more relevant to this feature request: When trying to add a ppx driver flag systematically to...

OK yes, I agree. I'm not sure how many different ppx_driver kinds you can build with `ppxlib` (it could simply be a historical artifact). But you'd most likely want `dune`...

> At first glance this seems like it's going to create you more work than it's ever going to save in the long run. You may be right about that!...

That generalization makes sense to me. In spirit, configuring a large set of projects in a consistent way is a good part of dunolint's motivations, and I have made that...

> would fixing ppxlib's driver to provide a consistent set of flags, regardless of what ppx-es are being linked help toward having a simple variable to store ppx driver flags...