On 15.03.23 18:44, Matthieu Baerts wrote: > Since v6.3, checkpatch.pl now complains about the use of "Closes:" tags > followed by a link [1]. It also complains if a "Reported-by:" tag is > followed by a "Closes:" one [2]. > > As detailed in the first patch, this "Closes:" tag is used for a bit of > time, mainly by DRM and MPTCP subsystems. It is used by some bug > trackers to automate the closure of issues when a patch is accepted. > > Because this tag is used for a bit of time by different subsystems and > it looks like it makes sense and it is useful for them, I didn't bother > Linus to get his permission to continue using it. If you think this is > necessary to do that up front, please tell me and I will be happy to ask > for his agreement. Due to how he reacted to some "invented" tags recently, I'd think it would be appropriate to CC him on this patchset, as he then can speak up if he wants to (and I assume a few more mails don't bother him). > The first patch updates the documentation to explain what is this > "Closes:" tag and how/when to use it. The second patch modifies > checkpatch.pl to stop complaining about it. I liked Andrew's `have been using "Addresses:" on occasion. [...] more humble [...]` comment. Sadly that tag is not supported by GitLab and GitHub. But well, "Resolves" is and also a bit more humble if you ask me. How about using that instead? Assuming that Konstantin can work with that tag, too, but I guess he can. I also wonder if the texts for the documentation could be shorter. Wouldn't something like this do? `Instead of "Link:" feel free to use "Resolves:" with an URL instead, if the issue was filed in a public bug tracker that will consider the issue resolved when it noticed that tag.` [s/Resolves/Closes/ if we stick to that] Side note: makes we wonder if we should go "all in" here to avoid confusion and allow "Resolves" everywhere, even for links to lore. > [...] Ciao, Thorsten
