On 7/8/24 04:14, Joseph Koshakow wrote: > Given the above and the fact that the patch is a breaking change, my > vote would still be to keep the current behavior and update the > documentation. Though I'd be happy to be overruled by someone with more > knowledge of triggers.
Thanks for that feedback. Based on that, the patch should be rejected.
Since there were a couple of other opinions early in the thread, I'll let it sit like that for now, and judgement can be passed at the end of the commitfest. Perhaps somebody else wants to chime in.
It is hard to say what should be expected behaviour in this case. I think the best is just to document this issue, and change nothing.