ChanServ changed the topic of #linux-msm to:
jacobk has joined #linux-msm
marvin24 has joined #linux-msm
marvin24_ has quit [Ping timeout: 480 seconds]
jhovold has joined #linux-msm
gnuiyl has quit []
zstas has joined #linux-msm
jacobk_ has joined #linux-msm
jacobk is now known as Guest8229
jacobk_ is now known as jacobk
Guest8229 has quit [Ping timeout: 480 seconds]
srinik has joined #linux-msm
zstas has quit [Ping timeout: 480 seconds]
pespin has joined #linux-msm
srinik has quit [Ping timeout: 480 seconds]
deathmist1 has joined #linux-msm
deathmist has quit [Ping timeout: 480 seconds]
srinik has joined #linux-msm
deathmist1 is now known as deathmist
sydarn has joined #linux-msm
srinik has quit [Ping timeout: 480 seconds]
jacobk_ has joined #linux-msm
jacobk is now known as Guest8281
jacobk_ is now known as jacobk
Guest8281 has quit [Ping timeout: 480 seconds]
<z3ntu> not msm-related but is there a way that dt-validate warns about deprecated properties being used? So far as far as I can tell "deprecated: true" is essentially invisible unless you read the schema yaml yourself
<bamse> z3ntu: i looked 2-3 months ago, and there's no code in the validator related to "deprecated"
<z3ntu> I also looked and didn't see anything, too bad
aklimov has quit [Ping timeout: 480 seconds]
Daanct12 has joined #linux-msm
Danct12 has quit [Read error: Connection reset by peer]
aklimov has joined #linux-msm
sydarn has quit [Quit: sydarn]
pespin has quit [Remote host closed the connection]