On Sat, Nov 2, 2019 at 11:04 PM Friedrich W. H. Kossebau
wrote:
>
> Am Donnerstag, 24. Oktober 2019, 10:50:07 CET schrieb laurent Montel:
> > When a compilation is broken by a new deprecated method we will fix it.
>
> First though lots of people run into the build error, and are annoyed by it.
>
>
On Wed, Nov 13, 2019 at 12:26 AM Luigi Toscano wrote:
>
> Roman Gilg ha scritto:
> > On Mon, Nov 11, 2019 at 10:58 PM Luigi Toscano
> > wrote:
> >>
> >> Roman Gilg ha scritto:
> >>> Hi,
> >>>
> >>> I just pushed commit mes
On Mon, Nov 11, 2019 at 10:58 PM Luigi Toscano wrote:
>
> Roman Gilg ha scritto:
> > Hi,
> >
> > I just pushed commit message policies to KScreen [1] and libkscreen
> > [2] (linked below from GitHub so they can be read with Markdown
> > formatted).
> >
Hi,
I just pushed commit message policies to KScreen [1] and libkscreen
[2] (linked below from GitHub so they can be read with Markdown
formatted).
I intend to revert in the future all manual commits to KScreen and
libkscreen deliberately ignoring the policies. Here "manual" means
here that I won
On Tue, Oct 15, 2019 at 8:12 PM Ben Cooksley wrote:
>
> On Wed, 16 Oct 2019, 05:17 Johan Ouwerkerk, wrote:
>> [...]
>
>
> It was complexity of that degree that I was primarily concerned about when
> people started pushing for being able to force push and use a rebase workflow.
>
> For a first ti
On Fri, Sep 13, 2019 at 3:47 PM David Edmundson
wrote:
>
> Within plasma we don't tend to have any "official" handover, though
> the bugzilla case is relevant. Let me know where you want bugs to be
> assigned to.
There is the repo metadata, which I think should be amended:
https://cgit.kde.org/sy
Hi,
since I am the only person responsible for bigger changes to
libkscreen and KScreen over months now I propose to take over
maintainership of libkscreen / KScreen. Actually I changed the
maintainership information already in code for KScreen with
https://phabricator.kde.org/D22468,
but I rememb
For KWin we think about a message guideline because our current best
practice that we got used to over time is just sometimes putting tags
in square brackets at the beginning of the subject line for indicating
the location of the change in code but somebody noted having a square
bracket in the begi
On Sat, Feb 23, 2019 at 10:45 AM Ben Cooksley wrote:
>
> Hi all,
>
> [...]
>
> Based on all of the above we'd like to propose migrating towards
> Gitlab. Comments?
Good decision. Hopefully the migration will start sooner than later.
Thank you for all your work on that.
You need to edit the height property (change) in the horizontal panel mode.
https://cgit.kde.org/plasma-workspace.git/commit/applets/digital-clock/package/contents/ui/DigitalClock.qml?id=90ea27f49c84f0dffbbf79b29eaa14c57f31a24d
gives you an idea how it should be done.
I'm against making this con
Please try again with kdesrc-build from current master. I just pushed
a patch (mentioned by Michael before) about not moving up the /usr
directory in multiple environment variables including
CMAKE_PREFIX_PATH, what might have overwritten your manual setting.
Regarding your CMakeCache.txt: /usr/loc
Hi Max,
sorry for my late reply. I was working on some larger project, which
took me away.
I'm no expert on the init sequence and also not on SysOps, but from a
developer perspective diverging from upstream by patching a major
software piece like plasma-workspace in order to solve a particular
se
Hi Max,
if you're using Plasma 5.11, then you don't need to look into the
"plasma-workspace/startkde/waitforname" folder, because 5.11 has it. So
the notifications should be delayed on your system already. But of course
you can still take a look and check the patch out, which added it [1],
becaus
13 matches
Mail list logo
