https://bugs.kde.org/show_bug.cgi?id=353983
Antonio Orefice changed:
What|Removed |Added
CC||kokok...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=241557
--- Comment #17 from Antonio Orefice ---
Any particular reason this bug is still marked as UNCONFIRMED (!?)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=241557
--- Comment #19 from Antonio Orefice ---
Yes, yes, i did not mean that.
I really mean just what i asked :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #12 from Antonio Orefice ---
For what is worth, the bug is present even in plasmoidviewer.
Just play with it and see how his memory usage grows with ease.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368838
Antonio Orefice changed:
What|Removed |Added
Summary|plasmashell keeps eating|plasmashell keeps eating
https://bugs.kde.org/show_bug.cgi?id=372739
Bug ID: 372739
Summary: Some effects goes slowmotion when vsync is disabled
Product: kwin
Version: 5.8.3
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity:
https://bugs.kde.org/show_bug.cgi?id=372739
--- Comment #1 from Antonio Orefice ---
Ok, i've to add several information to this report, sorry.
The slowness was due to a setting i have in my kwinrc:
MaxFPS=300
I have to specify it because:
1) with vsync disabled, kwin render frames at 60hz
https://bugs.kde.org/show_bug.cgi?id=372739
Antonio Orefice changed:
What|Removed |Added
Summary|Some effects goes |Vsync disabled: slowmotion
https://bugs.kde.org/show_bug.cgi?id=372739
--- Comment #3 from Antonio Orefice ---
Hi Martin, thanks for answering.
The real issue here, is that kwin is unable to detect the right refresh rate
when vsync is disabled.
Can we continue here or should i open another bug report about that?
Or maybe
https://bugs.kde.org/show_bug.cgi?id=372739
--- Comment #5 from Antonio Orefice ---
Hi again,
maybe there is a misunderstanding here, sorry.
The problem i have with limited framerate does not depend on the driver
settings,
I'm able to reproduce it even without nvi
https://bugs.kde.org/show_bug.cgi?id=372739
--- Comment #7 from Antonio Orefice ---
Created attachment 102386
--> https://bugs.kde.org/attachment.cgi?id=102386&action=edit
supportinformation from kwin when running without vsync enabled
--
You are receiving this mail because:
You are w
https://bugs.kde.org/show_bug.cgi?id=372739
--- Comment #8 from Antonio Orefice ---
and it picks:
Refresh Rate: 75.0247 for both monitors with and without tearing prevention
enabled, which should be fine...
What puzzles me is why window movements are:
*jerky:
with vsync disabled and screen
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #13 from Antonio Orefice ---
Created attachment 102436
--> https://bugs.kde.org/attachment.cgi?id=102436&action=edit
plasmoidviewer: memory maps, memory status and "valgrind --tool=memcheck
--leak-check=full" log
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #14 from Antonio Orefice ---
Created attachment 102437
--> https://bugs.kde.org/attachment.cgi?id=102437&action=edit
log with debug symbols enabled for qt5-declarative and qt5-base
Same as before, but with debug symbols for (what
https://bugs.kde.org/show_bug.cgi?id=372812
Antonio Orefice changed:
What|Removed |Added
CC||kokok...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=439689
--- Comment #19 from Antonio Orefice ---
Hi, i've seen kwin 5.24 is out.
Any news on this?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443434
Antonio Orefice changed:
What|Removed |Added
CC||kokok...@gmail.com
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=443434
--- Comment #4 from Antonio Orefice ---
(In reply to Vlad Zahorodnii from comment #2)
> Given the wayland issues and in part maintenance costs, this change
> drops the resize effect. Note that it can be still reimplemented without
> kwin cor
https://bugs.kde.org/show_bug.cgi?id=467604
Bug ID: 467604
Summary: Kate/kwrite unuseful wasted space that also don't
allow to grab scrollbars near the edge of the screen
when maximized.
Classification: Applications
Prod
https://bugs.kde.org/show_bug.cgi?id=467604
--- Comment #1 from Antonio Orefice ---
Created attachment 157438
--> https://bugs.kde.org/attachment.cgi?id=157438&action=edit
Empty toolbars expanded
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=467604
--- Comment #2 from Antonio Orefice ---
Created attachment 157439
--> https://bugs.kde.org/attachment.cgi?id=157439&action=edit
Can't scroll on the edge of a maximized window, see mouse shape.
--
You are receiving this mail beca
https://bugs.kde.org/show_bug.cgi?id=467604
--- Comment #3 from Antonio Orefice ---
Created attachment 157441
--> https://bugs.kde.org/attachment.cgi?id=157441&action=edit
Right side bar expanded too, the reason why scrolling on the edge isn't working
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=434829
--- Comment #9 from Antonio Orefice ---
And again, it resets luts on resolution changes.
Also, the previous hack does not work anymore.
Could you please suggest another workaround if fixing this issue is not an
option, please?
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=482876
Bug ID: 482876
Summary: Some applications won't go fullscreen on X11 when
screen scaling is enabled
Classification: Plasma
Product: kwin
Version: 6.0.1
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=482876
--- Comment #1 from Antonio Orefice ---
Some screen scaling setting allow for fullscreen, like 200%
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482878
Bug ID: 482878
Summary: On x11 you cannot drag windows offscreen left or up if
compositor is disabled
Classification: Plasma
Product: kwin
Version: 6.0.1
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=482878
Antonio Orefice changed:
What|Removed |Added
Summary|On x11 you cannot drag |Problems on x11 when
https://bugs.kde.org/show_bug.cgi?id=482878
Antonio Orefice changed:
What|Removed |Added
Summary|Problems on x11 when|Problems on x11 when
https://bugs.kde.org/show_bug.cgi?id=482878
--- Comment #2 from Antonio Orefice ---
Just noticed that when the compositor is active and the window is offscreen,
mouse clicks are offsetted.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=434829
Antonio Orefice changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|UPSTREAM
https://bugs.kde.org/show_bug.cgi?id=434829
Antonio Orefice changed:
What|Removed |Added
Resolution|UPSTREAM|---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=434829
--- Comment #14 from Antonio Orefice ---
Ok, can plasma just stop resetting the lut when resolution changes?
I've edited the bug title to reflect that.
If even that is not possible, feel free to close.
Have a good day.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=434829
--- Comment #15 from Antonio Orefice ---
(In reply to Zamundaaa from comment #12)
> KWin does not have any information about what other applications are doing
> or not doing with the lut, so it can't keep your use case working.
In case you
https://bugs.kde.org/show_bug.cgi?id=434829
--- Comment #17 from Antonio Orefice ---
Ok, I'm just going to use xrandr and trigger a lut reload.
If anyone needs:
koko@Gozer# cat /koko/scripts/benq.keep.lut.sh
#!/bin/bash
dispwin -d 1 -s /koko/tmp/1.lut
dispwin -d 2 -s /koko/tmp/
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #77 from Antonio Orefice ---
Just tried with an i5-1035g1 under wayland with its gpu that should be far more
performant than my haswell, but still on the logout screen mouse cursor was
stuttering (a lot) under wayland on the newer cpu and
https://bugs.kde.org/show_bug.cgi?id=480306
Bug ID: 480306
Summary: Audio balance is reset/lost when setting volume "too"
high or "too" low.
Classification: Plasma
Product: plasma-pa
Version: unspecified
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=480306
--- Comment #1 from Antonio Orefice ---
Easy fix would be to put a minimum and a maximum to allowed volume range when
panning is in use.
If one of the slider reaches 100, don't move the others
If one of the slider reaches 0, don't move
https://bugs.kde.org/show_bug.cgi?id=480306
--- Comment #3 from Antonio Orefice ---
(In reply to fanzhuyifan from comment #2)
> On plasma 6, I can only reproduce this when the volume is set to 0 --
> balance is lost afterwards. The balance is preserved when I set the volume
&g
https://bugs.kde.org/show_bug.cgi?id=480306
--- Comment #6 from Antonio Orefice ---
(In reply to fanzhuyifan from comment #5)
> You could also share a link to a screencast of the problem you are seeing.
yeah, ofc. but the problem seems pretty clear, we can avoid the bloat when
plain text
https://bugs.kde.org/show_bug.cgi?id=452117
Bug ID: 452117
Summary: kwin on wayland not using hardware cursor
Product: kwin
Version: 5.24.4
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=452117
--- Comment #1 from Antonio Orefice ---
[plasmauser@Gozer tmp]$ zgrep Cursor wayland-session.log.gz
kwin_wayland_drm: Plane 41 has properties "type"="Cursor", "SRC_X"=0,
"SRC_Y"=0, "SRC_W"=0, "S
https://bugs.kde.org/show_bug.cgi?id=452119
Bug ID: 452119
Summary: Poor performance on intel igp on wayland versus Xorg
Product: kwin
Version: 5.24.4
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=452117
--- Comment #2 from Antonio Orefice ---
Created attachment 147873
--> https://bugs.kde.org/attachment.cgi?id=147873&action=edit
modetest from libdrm
It seems hardware cursor is available.
--
You are receiving this mail because:
You are w
https://bugs.kde.org/show_bug.cgi?id=452117
Antonio Orefice changed:
What|Removed |Added
Summary|kwin on wayland not using |kwin on wayland: mouse
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #4 from Antonio Orefice ---
(In reply to Zamundaaa from comment #3)
> > But what REALLY helps, is enabling the Show FPS effect
>
> Does the GPU or memory clock go up if you enable it?
If I remember right, it goes from 2mhz to
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #5 from Antonio Orefice ---
(In reply to Zamundaaa from comment #3)
> > But what REALLY helps, is enabling the Show FPS effect
>
> Does the GPU or memory clock go up if you enable it?
Enabling show fps effects bump the gpu
https://bugs.kde.org/show_bug.cgi?id=452117
--- Comment #5 from Antonio Orefice ---
(In reply to Zamundaaa from comment #4)
> It's more or less an issue with how the atomic modesetting API currently
> works, changing that is not trivial but being worked on. You can use the
> enviro
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #7 from Antonio Orefice ---
(In reply to Zamundaaa from comment #6)
> What does the memory clock do with the fps effect? GPU core clock is not the
> single deciding factor on performance
If you are asking me, I've no idea.
I
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #8 from Antonio Orefice ---
Aye, i've read better, sorry.
I don't know how to read current memory clock speed. Do you have advices?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #10 from Antonio Orefice ---
(In reply to Zamundaaa from comment #9)
> I don't know how to check the memory clock on Intel systems, searching for
> it doesn't yield results for the dynamic memory speed either.
>
> We
https://bugs.kde.org/show_bug.cgi?id=452117
--- Comment #7 from Antonio Orefice ---
(In reply to Nate Graham from comment #6)
> FWIW I've also been running with KWIN_DRM_NO_AMS=1, just because it keeps
> kwin_wayland's CPU usage down. I haven't noticed any regressions.
Ye
https://bugs.kde.org/show_bug.cgi?id=435423
--- Comment #10 from Antonio Orefice ---
(In reply to Nate Graham from comment #8)
> Can reproduce 100% on Wayland, but not X11, interestingly.
I have to point out that this bug is not about wayland not sliding and morphing
the shape of the po
https://bugs.kde.org/show_bug.cgi?id=442129
Bug ID: 442129
Summary: Window resize effect: some apps becomes transparents
for a while.
Product: kwin
Version: 5.22.3
Platform: Other
OS: Linux
Statu
https://bugs.kde.org/show_bug.cgi?id=442129
--- Comment #1 from Antonio Orefice ---
Created attachment 141362
--> https://bugs.kde.org/attachment.cgi?id=141362&action=edit
resize konsole and dolphin
forgot the attachment
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=451531
Bug ID: 451531
Summary: Dual head, different resolutions, clone mode ->
missing panel.
Product: KScreen
Version: 5.24.2
Platform: Archlinux Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=434829
--- Comment #8 from Antonio Orefice ---
The situation is improved.
Now kwin does not reset the lut anymore when changing resolution, but just when
it starts.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=451590
Antonio Orefice changed:
What|Removed |Added
CC||kokok...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=451590
--- Comment #26 from Antonio Orefice ---
For me, it is not (only) a matter of having a second screen or not.
Yes, having multiple screens make the things worse for me too, but it is just
because my igp is more taxed that way.
Indeed, on a single
https://bugs.kde.org/show_bug.cgi?id=439689
Antonio Orefice changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=439689
--- Comment #15 from Antonio Orefice ---
Maybe related, or not, we lost xfade on window resize too when using the resize
effect that scales the window texture.
I managed to bring xfade for (un)maximize effect by downgrading
kwin,kdecoration and
https://bugs.kde.org/show_bug.cgi?id=424825
--- Comment #6 from Antonio Orefice ---
21.08.2 is still affected
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=435423
--- Comment #6 from Antonio Orefice ---
Used to work with some glitches in plasma 5.22.5 due to this being fixed:
https://bugs.kde.org/show_bug.cgi?id=439689
Now the same bug has returned and this is following.
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=439689
--- Comment #16 from Antonio Orefice ---
f432ba78 | GOOD
ebc785167 | BAD
I'm unable to build in between, sorry.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=427417
Bug ID: 427417
Summary: Changing Shading -> contrast does not change anything.
Product: Oxygen
Version: 5.19.5
Platform: Other
OS: Linux
Status: REPORTED
Severit
https://bugs.kde.org/show_bug.cgi?id=427417
--- Comment #1 from Antonio Orefice ---
i noticed that the value for "contrast" in kdeglobals in [KDE] section is not
updated by the color config utility.
But if i chang it manualy and logout/login, then the contrast changes.
I'm
https://bugs.kde.org/show_bug.cgi?id=427417
Antonio Orefice changed:
What|Removed |Added
Product|Oxygen |kde
Component|style
https://bugs.kde.org/show_bug.cgi?id=427417
--- Comment #2 from Antonio Orefice ---
Hi Nate,
Initially i identified the component as Oxygen, but i noticed that the color
systemsettings module just does not update che "contrast" setting into the
kdeglobals file.
If i change it manual
https://bugs.kde.org/show_bug.cgi?id=424825
Antonio Orefice changed:
What|Removed |Added
Resolution|DUPLICATE |---
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=424825
Antonio Orefice changed:
What|Removed |Added
Summary|yakuake 20.04.3 wont go |yakuake wont go fullscreen
https://bugs.kde.org/show_bug.cgi?id=438874
--- Comment #35 from Antonio Orefice ---
(In reply to Attila from comment #34)
> Here is my workaround until this bug has been fixed.
> You need two USB devices. Let's call the first one "a dummy USB device".
>
> 1. Just P
https://bugs.kde.org/show_bug.cgi?id=439689
Bug ID: 439689
Summary: Crossfade window effect does not work
Product: kwin
Version: 5.22.3
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=439689
Antonio Orefice changed:
What|Removed |Added
Summary|Crossfade window effect |Maximize effect: no more
https://bugs.kde.org/show_bug.cgi?id=438079
Antonio Orefice changed:
What|Removed |Added
CC||kokok...@gmail.com
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=438079
Antonio Orefice changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=438478
Antonio Orefice changed:
What|Removed |Added
CC||kokok...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=430521
Antonio Orefice changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=430521
--- Comment #27 from Antonio Orefice ---
I've no lines beginning with "Window-Maximized", but i've just this:
"HDMI1 HDMI2 Window-Maximized 800x600=true"
Deleted, killed dolphin, but the problem persisted.
--
You are re
https://bugs.kde.org/show_bug.cgi?id=430521
--- Comment #29 from Antonio Orefice ---
Hi Nate, i've attached one in the past in the other bug report:
https://bugs.kde.org/show_bug.cgi?id=434825
https://bugs.kde.org/attachment.cgi?id=137023
--
You are receiving this mail because:
Yo
https://bugs.kde.org/show_bug.cgi?id=430521
--- Comment #30 from Antonio Orefice ---
Created attachment 140348
--> https://bugs.kde.org/attachment.cgi?id=140348&action=edit
dolphinrc
(In reply to Antonio Orefice from comment #29)
> Hi Nate, i've attached one in the past i
https://bugs.kde.org/show_bug.cgi?id=430521
--- Comment #31 from Antonio Orefice ---
Sorry for the confusion,
I've to retract my observations in comment 25 about ~/.config/dolphinrc, (i
read and spoke about dolphinui.rc, ,sorry)
Removing ~/.config/dolphinrc, does not change a thing.
Sorr
https://bugs.kde.org/show_bug.cgi?id=430521
--- Comment #32 from Antonio Orefice ---
Created attachment 140350
--> https://bugs.kde.org/attachment.cgi?id=140350&action=edit
other resize problems when in dual panel mode
I've found that even using standard/shipped config files, ther
https://bugs.kde.org/show_bug.cgi?id=430521
Antonio Orefice changed:
What|Removed |Added
Status|NEEDSINFO |REOPENED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=430521
--- Comment #35 from Antonio Orefice ---
Unfortunately on single screen setup (another system) things do not change.
About the other thing i reported, i think they are related in the way that
"dolphin is unable to correctly resize internal wi
https://bugs.kde.org/show_bug.cgi?id=430521
--- Comment #36 from Antonio Orefice ---
(In reply to Nate Graham from comment #34)
> Thanks for the config file. I still cannot reproduce the issue even when I
> use it on my own Dolphin. :(
Given the config files posted, a way (not the only w
https://bugs.kde.org/show_bug.cgi?id=430521
--- Comment #37 from Antonio Orefice ---
I bisected the issue, but even if i found the "bad" commit,
it is not much useful, because it just exposes a bug introduced earlier and i
cannot determine when using git bisect:
In the past, the lo
https://bugs.kde.org/show_bug.cgi?id=440382
Bug ID: 440382
Summary: Main toolbar elements messed up on (un)maximize then
using split view.
Product: dolphin
Version: 21.07.80
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=440382
Antonio Orefice changed:
What|Removed |Added
Summary|Main toolbar elements |Main toolbar elements
https://bugs.kde.org/show_bug.cgi?id=434825
Antonio Orefice changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=430521
--- Comment #40 from Antonio Orefice ---
*** Bug 434825 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=440382
Antonio Orefice changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=430521
--- Comment #41 from Antonio Orefice ---
*** Bug 440382 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=439689
--- Comment #2 from Antonio Orefice ---
Created attachment 140468
--> https://bugs.kde.org/attachment.cgi?id=140468&action=edit
maximize/minimize, no crossfade video.
Oh weird, it is broken on 3 systems here.
Fun fact:
the first morphing t
https://bugs.kde.org/show_bug.cgi?id=439689
Antonio Orefice changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=439689
Antonio Orefice changed:
What|Removed |Added
Version|5.22.3 |5.21.90
--- Comment #5 from Antonio Orefice
https://bugs.kde.org/show_bug.cgi?id=438458
Antonio Orefice changed:
What|Removed |Added
Product|yakuake |kwin
Component|general
https://bugs.kde.org/show_bug.cgi?id=438458
--- Comment #8 from Antonio Orefice ---
Works fine till kwin 5.21.90
Downgrading it makes it work (have to downgrade kwayland-server to the same
version too to make it happy)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=435378
Antonio Orefice changed:
What|Removed |Added
Version|unspecified |5.21.90
Component|compositing
https://bugs.kde.org/show_bug.cgi?id=435378
--- Comment #3 from Antonio Orefice ---
Since downgrading kwin to the now reported version solves the issue, i think
the problem lies there.
This: https://bugs.kde.org/show_bug.cgi?id=438458
seems to be a dupe.
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=438458
--- Comment #9 from Antonio Orefice ---
Bisected. The offending commit is:
koko@Gozer# git bisect good
47113e09b8a80497463725a795728a34e9db940c is the first bad commit
commit 47113e09b8a80497463725a795728a34e9db940c
Author: Vlad Zahorodnii
Date
https://bugs.kde.org/show_bug.cgi?id=435378
--- Comment #4 from Antonio Orefice ---
Bisected. The offending commit is:
koko@Gozer# git bisect good
47113e09b8a80497463725a795728a34e9db940c is the first bad commit
commit 47113e09b8a80497463725a795728a34e9db940c
Author: Vlad Zahorodnii
Date
1 - 100 of 308 matches
Mail list logo
