03:53 kchibisov: What does the "When the seat has the keyboard capability the text-input focus follows the keyboard focus." in text_input_v3 protocol on ::enter event? Does it mean that text_input_v3::enter is redundant if the keyboard is bound, and I should handle text_input_v3 from the keyboard handlers (I'd assume not)?
03:55 kchibisov: The `text_input_v3::enable` says "Requests text input on the surface previously obtained from the enter event.", but what `enter` event?
11:54 davidre: emersion: This is my first mesa patch, do I need to do something or wait for someone with powers to merge eventually?
11:54 emersion: davidre: i generally wait a few days before merging in case someone else has something to say
11:54 emersion: please ping me in a few days if it's still not merged
11:54 davidre: Ok, I was not sure as I saw people assigning their MRs to the bot
11:55 emersion: davidre: btw mayeb you want to add a Fixes or `Cc: mesa-stable`
11:55 emersion: for the patch to be propagated in stable trees
11:55 davidre: Will do that then
11:55 davidre: I also have to add your reviewed-by to the commit message I think?
11:57 emersion: it's slightly better, but mesa has a mixed policy with R-b tags iirc
11:57 emersion: some want it, some don't care…
12:01 pq: davidre, "merge" in Mesa means "assign to Marge". It is mostly for practical reasons due to the sheer volume of MRs landing all the time and the CI.
12:01 davidre: Thanks!