Hello, On Tue 08 Mar 2022 at 04:45pm +01, Lucas Nussbaum wrote:
> 1/ the arguments about using patches to track changes to upstream code. > Among the ~600 packages in that potential MBF, there are still many that > make changes to upstream code, which are not properly documented. I > believe that it is widely accepted that seperate patches in > debian/patches/ are the recommended way to manage changes to upstream code > (good way to help with those changes getting reviewed, getting merged > upstream, etc.) ... or a git workflow which has the changes represented as git commits, rather than files under d/patches. -- Sean Whitton
