> On Set. 1, 2014, 4:53 p.m., David Edmundson wrote:
> > I need some the concept explaining, why would a developer set a
> > fallbackpackage?
> > Is it not always org.kde.breeze.desktop?
>
> Marco Martin wrote:
> It would usually be the packagestructure setting it, in initPackage(), so
> s
> On Set. 1, 2014, 4:53 p.m., David Edmundson wrote:
> > I need some the concept explaining, why would a developer set a
> > fallbackpackage?
> > Is it not always org.kde.breeze.desktop?
>
> Marco Martin wrote:
> It would usually be the packagestructure setting it, in initPackage(), so
> s
> On Sept. 1, 2014, 4:53 p.m., David Edmundson wrote:
> > I need some the concept explaining, why would a developer set a
> > fallbackpackage?
> > Is it not always org.kde.breeze.desktop?
>
> Marco Martin wrote:
> It would usually be the packagestructure setting it, in initPackage(), so
>
> On Set. 1, 2014, 4:53 p.m., David Edmundson wrote:
> > I need some the concept explaining, why would a developer set a
> > fallbackpackage?
> > Is it not always org.kde.breeze.desktop?
>
> Marco Martin wrote:
> It would usually be the packagestructure setting it, in initPackage(), so
> s
> On Sept. 1, 2014, 4:53 p.m., David Edmundson wrote:
> > I need some the concept explaining, why would a developer set a
> > fallbackpackage?
> > Is it not always org.kde.breeze.desktop?
>
> Marco Martin wrote:
> It would usually be the packagestructure setting it, in initPackage(), so
>
> On Set. 1, 2014, 4:53 p.m., David Edmundson wrote:
> > I need some the concept explaining, why would a developer set a
> > fallbackpackage?
> > Is it not always org.kde.breeze.desktop?
>
> Marco Martin wrote:
> It would usually be the packagestructure setting it, in initPackage(), so
> s
> On Sept. 1, 2014, 4:53 p.m., David Edmundson wrote:
> > I need some the concept explaining, why would a developer set a
> > fallbackpackage?
> > Is it not always org.kde.breeze.desktop?
>
> Marco Martin wrote:
> It would usually be the packagestructure setting it, in initPackage(), so
>
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120029/
---
(Updated Sept. 1, 2014, 7:04 p.m.)
Status
--
This change has been ma
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120029/#review65661
---
Ship it!
Ship It!
- David Edmundson
On Sept. 1, 2014, 6:37
> On Sept. 1, 2014, 4:53 p.m., David Edmundson wrote:
> > I need some the concept explaining, why would a developer set a
> > fallbackpackage?
> > Is it not always org.kde.breeze.desktop?
>
> Marco Martin wrote:
> It would usually be the packagestructure setting it, in initPackage(), so
>
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120029/
---
(Updated Sept. 1, 2014, 6:37 p.m.)
Review request for KDE Frameworks and
> On Sept. 1, 2014, 4:53 p.m., David Edmundson wrote:
> > I need some the concept explaining, why would a developer set a
> > fallbackpackage?
> > Is it not always org.kde.breeze.desktop?
>
> Marco Martin wrote:
> It would usually be the packagestructure setting it, in initPackage(), so
>
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120029/
---
(Updated Sept. 1, 2014, 5:24 p.m.)
Review request for KDE Frameworks and
> On Sept. 1, 2014, 4:53 p.m., David Edmundson wrote:
> > I need some the concept explaining, why would a developer set a
> > fallbackpackage?
> > Is it not always org.kde.breeze.desktop?
It would usually be the packagestructure setting it, in initPackage(), so
setFallbackPackage follows the s
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120029/#review65648
---
I need some the concept explaining, why would a developer set
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120029/
---
Review request for KDE Frameworks and Plasma.
Repository: plasma-framewor
16 matches
Mail list logo