ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput | register your nick to speak
soreau has joined #wayland
jess has quit []
MadcapJake has joined #wayland
soreau has quit [Read error: Connection reset by peer]
soreau has joined #wayland
Dami-star has joined #wayland
Dami_Lu has quit [Read error: Connection reset by peer]
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
robobub_ has joined #wayland
Company has quit [Read error: No route to host]
Company has joined #wayland
Company has quit [Read error: Connection reset by peer]
godvino has quit [Read error: Connection reset by peer]
jmdaemon has quit [Ping timeout: 480 seconds]
Szadek has joined #wayland
clem_ has quit [Quit: Clem_]
clem_ has joined #wayland
sythemeta847[m] has joined #wayland
fmuellner has quit []
fmuellner has joined #wayland
fmuellner has quit [Ping timeout: 480 seconds]
devilhorns has joined #wayland
nerdopolis has joined #wayland
Szadek has quit [Quit: WeeChat 3.8]
Szadek has joined #wayland
<emersion>
zzag: yeah, because GitLab squashed everything
<ifreund>
Time to disable squash merging then?
<emersion>
but then it would just push the 27 individual commits which isn't a lot better
<emersion>
but yeah
<emersion>
I need to be more careful, really missed that when clicking
<ifreund>
Well, the the merger would have to manually squash and force push the branch
<ifreund>
so that CI runs on the (squashed) commit to be merged before the button can be pressed
<ifreund>
gitlab allowing you to merge a commit without CI passing on it seems like a gitlab/configuration issue, not your fault emersion
<zzag>
ifreund: if you click "squash commits", there's another checkbox to allow editing the commit message
<jadahl>
ifreund: the merger shouldn't squash, the contributor should
<ifreund>
zzag: it seems to me that however the commit message turns out CI is not run on the resulting commit before merging to master
<ifreund>
if it was, emersion wouldn't have been able to merge that commit
<zzag>
jadahl: agreed. kde-wise we permit such workflows, but I hate it because it's unclear what the author wants to get in master branch
<zzag>
also if the MR contains 30, 40, 50 or more commits, it's barely reviewable
<ifreund>
jadahl: sure, that would be ideal. For my projects I sometimes squash things myself while merging rather than bug the contributor/teach them how. Mostly just for drive-by contributions though
<jadahl>
yea, it's also much harder to backport things if it goes back and forth changing things here and there before finally ending with the final result
<emersion>
alright, let's disable squash then
<emersion>
done
<elibrokeit>
ifreund: CI does not need to run on the resulting commit, why would you remotely care about that?
<ifreund>
elibrokeit: in this case the CI lints the commit message to ensure it has a Signed-of-by: trailer
<ifreund>
s/of/off/
<elibrokeit>
It's logically wrong for this to be done by CI, but software forges rarely allow you to set up pre-receive githooks
<elibrokeit>
as far as CI goes, you only really care that the same tree object is tested, this logical rule covers squash and rebase merges as a side effect -- and has no effect on fast-forward merges -- by asserting the desire that merged MRs should only be merged when the resulting software state is tested regardless of how you edit commit messages during the merge itself
<elibrokeit>
unfortunately this is not necessarily possible either
<elibrokeit>
which is why e.g. marge-bots exist
<mvlad>
short psa, tomorrow is the alpha release for weston 12.
i509vcb has quit [Quit: Connection closed for inactivity]
Ermine has quit [Remote host closed the connection]
Ermine has joined #wayland
Fxzxmic has joined #wayland
zttlinux_ has quit []
Szadek has quit [Ping timeout: 480 seconds]
eroux has joined #wayland
Szadek has joined #wayland
caveman has quit [Remote host closed the connection]
caveman has joined #wayland
Fxzxmic has quit [Ping timeout: 480 seconds]
Szadek has quit [Ping timeout: 480 seconds]
Szadek has joined #wayland
rv1sr has joined #wayland
fmuellner has joined #wayland
fmuellner has quit []
fmuellner has joined #wayland
Fxzxmic has joined #wayland
fullstop_ has joined #wayland
cphealy has quit [Remote host closed the connection]
cphealy has joined #wayland
kelnos has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
kelnos has joined #wayland
fullstop has quit [Ping timeout: 480 seconds]
fmuellner_ has joined #wayland
fmuellner has quit [Ping timeout: 480 seconds]
fmuellner_ has quit [Read error: Connection reset by peer]
fmuellner has joined #wayland
devilhorns has quit [Quit: Leaving]
fmuellner has quit [Remote host closed the connection]
MajorBiscuit has quit [Ping timeout: 480 seconds]
fmuellner has joined #wayland
Fxzx_mic has joined #wayland
Fxzxmic has quit [Ping timeout: 480 seconds]
Fxzx_mic is now known as Fxzxmic
Fxzxmic has quit [Remote host closed the connection]
kts has joined #wayland
Fxzxmic has joined #wayland
fmuellner has quit [Ping timeout: 480 seconds]
Fxzxmic has quit [Remote host closed the connection]
tzimmermann has quit [Quit: Leaving]
kts has quit [Quit: Konversation terminated!]
pochu has quit [Quit: leaving]
cool110 has quit [Remote host closed the connection]
cool110 has joined #wayland
dcz has joined #wayland
Cyrinux9 has quit []
junaid has joined #wayland
dcz_ has quit [Ping timeout: 480 seconds]
Cyrinux9 has joined #wayland
kasper93 has quit [Remote host closed the connection]
_DOOM_ has joined #wayland
<_DOOM_>
How would a compositor in practice make backwards compatible code for protocols?
MajorBiscuit has joined #wayland
junaid has quit [Remote host closed the connection]
Narrat has joined #wayland
Leopold__ has joined #wayland
Leopold_ has quit [Ping timeout: 480 seconds]
<kennylevinsen>
_DOOM_: it would check the protocol version of the bound global object. Usually all it needs to do is filter newer events, but it could switch implementation if things are vastly different.
<_DOOM_>
Would using the resource version be a good method for checking protocol version?
<JoshuaAshton>
pq: Didn't see your ping... I need to get my IRC client to stop replaying people disconnecting/reconnecting >.>
dcz has quit [Ping timeout: 480 seconds]
<JoshuaAshton>
scRGB has 709 primaries, but can express any perceptible or non-perceptible color due to it having negative values
<JoshuaAshton>
When considering games, you should consider that typically games and game developers don't know what a primary is :p
<JoshuaAshton>
They were authored for whatever they were displayed on
<JoshuaAshton>
Game developers using scRGB are probably taking their existing pipeline that outputs to sRGB and just changing their tonemapping step and buffer format
<JoshuaAshton>
That's not to say that no-one is using negative stuff in scRGB though
<JoshuaAshton>
but it is to say that, when you are outputing to 2020 HDR10 PQ anyway (nobody actually supports scRGB on the display side despite there being a DP entry for it), the best way is to just do 709 -> 2020 with a CTM then encode as PQ
<JoshuaAshton>
Like, if you are wanting to scanout a scRGB buffer, it's going to have to go to PQ
<JoshuaAshton>
You could do PQ with 709 primaries I guess -- but it's a gamble whether monitors actually respect the colorspace packet in HDR mode, there's quite a few that just go straight to 2020, and also some that stay in 709 and only go to 2020 when you send the colorimetry packet
<JoshuaAshton>
That also wouldn't handle negatives
<JoshuaAshton>
So ime, PQ + 2020 is really your only options if you want to handle broken displays.
c6ristian has quit [Ping timeout: 480 seconds]
fmuellner has joined #wayland
mvlad has quit [Remote host closed the connection]