On Sat, Feb 1, 2025 at 10:14 AM Abou Al Montacir <abou.almonta...@sfr.fr> wrote: > With regards to other possible values (No, NotNeeded), I find it a bit hacky > to use this field to provide an upstream bug URL. > I would completely remove this practice and keep this field human readable > and understandable to be a simple tri-state field (Yes, No, Not-Needed).
The vast majority disagree with you on the Forwarded field (4000ish to almost 600) but Forwarded: yes is used a lot. https://codesearch.debian.net/search?q=path%3Adebian%2Fpatches+Forwarded%3A+yes https://codesearch.debian.net/search?q=path%3Adebian%2Fpatches+Forwarded%3A+http A Forwarded link is human-readable and machine-readable. Also, Github and Gitlab separate issues from merge requests so it's possible to have two different upstream links. Personally, I would probably just use the merge request link instead of the issue link in this case though. Thank you, Jeremy Bícha
