On 2023-03-07 13:12, Friedrich W. H. Kossebau wrote:
Am Dienstag, 7. März 2023, 02:51:06 CET schrieb Aleix Pol:
Having ninja/make do this dependency generation can end up being more
work than worth it because then we need to have a static list
Such static list could be generated by scripty
On 2022-07-13 06:03, Luca Beltrame wrote:
In data martedì 12 luglio 2022 16:52:21 CEST, Nate Graham ha scritto:
Hello Nate,
+Fabian Vogt and Luca Beltrame specifically
Thanks, that's a relief! Does this looks legit enough for openSUSE to
stop patching out the KUSerFeedback integration?
In
On 2022-05-16 19:38, Alexander Neundorf wrote:
On Dienstag, 3. Mai 2022 18:43:48 CEST Méven wrote:
Le mar. 3 mai 2022 à 18:25, Thomas Friedrichsmeier <
thomas.friedrichsme...@kdemail.net> a écrit :
> On Tue, 3 May 2022 10:35:20 +0200
>
> Méven wrote:
> > I am guessing you are using cmake >=
On 2022-05-10 15:33, Nate Graham wrote:
On 5/10/22 04:15, Ingo Klöcker wrote:
https://manifesto.kde.org/commitments/
I don't see anything in there that would force the same merge workflow
on all
KDE projects. In my view the merge workflow is comparable to the
coding style.
Regards,
Ingo
Hi,
we will change KWrite to re-use the Kate codebase.
As side-effect, KWrite will like Kate now support opt-in telemetry via
KUserFeedback (can be even deactivated fully during compile time, purely
optional dependency).
The code is the same as used in Kate, the relevant merge request for
On 2021-09-06 11:48, Ben Cooksley wrote:
On Mon, Sep 6, 2021 at 9:00 PM Tom Zander wrote:
On zondag 5 september 2021 08:13:09 CEST Ben Cooksley wrote:
In terms of the format of the 'Dependencies' section,
Playing with kde-build script and noticing the fast growing
dependency trees we have
