On Friday, September 27, 2013 19:37:57 Mark wrote:
> I think one can very easily expect a part called "private" to be just that
> and that it should not be included. If one does do that then that person
> deserves the pain when the private api changes. I don't think you should go
> to private.org.k
On Wed, Sep 25, 2013 at 11:21 PM, Sebastian Kügler wrote:
> On Wednesday, September 25, 2013 17:51:41 Mark wrote:
> > Doesn't your naming proposal completely ruin the org.kde.* stuff? Up
> until
> > now i could fairly safely assume that all QML KDE imports where hidden
> > under org.kde.* but tha
Hi,
Not sure if you looked around a bit, but... there is a huge button at
https://bugs.kde.org/ for filing a bug. Do search for your problem via the
search function first! If someone else filed a bug for the problem you want
to report, then simply acknowledge the problem or keep an eye on the
exis
Hi All,
Can anyone please tell me how to file a bug ?
--
Regards
Garvit Sharma
Computer Science and Engineering
UG Final year
LNM IIT, Jaipur
*No Body is a Scholar by birth, its only hard work and strong determination
that makes him master.*
*
*
>> Visit http://mail.kde.org/mailman/listinfo/k
On Friday 27 September 2013 12:40:13 Sebastian Kügler wrote:
> On Thursday, September 26, 2013 22:08:32 Milian Wolff wrote:
> > why do we have to set much redundant information in .cpp/KAboutData which
> > is already somewhat defined by the KPluginInfo i.e. .desktop file?
> >
> > Point in case: K
On Thursday, September 26, 2013 22:08:32 Milian Wolff wrote:
> why do we have to set much redundant information in .cpp/KAboutData which
> is already somewhat defined by the KPluginInfo i.e. .desktop file?
>
> Point in case: KPluginSelector e.g. shows the Comment entry of the .desktop
> file. If
