On Sunday 12 October 2014 22:57:33 David Faure wrote:
> On Saturday 11 October 2014 16:40:55 Dominik Haumann wrote:
> > Hi all,
> >
> > imho, these are changes that get mostly unnoticed, and hence close to no
> > one will use this feature. I personally would find it very cool if there
> > were lot
On Saturday 11 October 2014 16:40:55 Dominik Haumann wrote:
> Hi all,
>
> imho, these are changes that get mostly unnoticed, and hence close to no one
> will use this feature. I personally would find it very cool if there were
> lots and lots of blogs on the planet for these technical details. It
Hi all,
imho, these are changes that get mostly unnoticed, and hence close to no one
will use this feature. I personally would find it very cool if there were lots
and lots of blogs on the planet for these technical details. It would also
communicate a bit more of the internals to potentially n
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120099/
---
(Updated Oct. 7, 2014, 8:04 p.m.)
Status
--
This change has been mar
> On Oct. 5, 2014, 5:58 p.m., Christoph Feck wrote:
> > Sorry for chiming in late, just noticed the commit.
> >
> > Any reason why the resource is checked first, not last?
> >
> > If the programmer decides to use the resource, the "locateAll" effectively
> > turns into a "locateNone". Not real
> On Oct. 5, 2014, 5:58 p.m., Christoph Feck wrote:
> > Sorry for chiming in late, just noticed the commit.
> >
> > Any reason why the resource is checked first, not last?
> >
> > If the programmer decides to use the resource, the "locateAll" effectively
> > turns into a "locateNone". Not real
> On oct. 5, 2014, 5:58 p.m., Christoph Feck wrote:
> > Sorry for chiming in late, just noticed the commit.
> >
> > Any reason why the resource is checked first, not last?
> >
> > If the programmer decides to use the resource, the "locateAll" effectively
> > turns into a "locateNone". Not real
> On oct. 5, 2014, 5:58 p.m., Christoph Feck wrote:
> > Sorry for chiming in late, just noticed the commit.
> >
> > Any reason why the resource is checked first, not last?
> >
> > If the programmer decides to use the resource, the "locateAll" effectively
> > turns into a "locateNone". Not real
> On Oct. 5, 2014, 5:58 p.m., Christoph Feck wrote:
> > Sorry for chiming in late, just noticed the commit.
> >
> > Any reason why the resource is checked first, not last?
> >
> > If the programmer decides to use the resource, the "locateAll" effectively
> > turns into a "locateNone". Not real
> On oct. 5, 2014, 5:58 p.m., Christoph Feck wrote:
> > Sorry for chiming in late, just noticed the commit.
> >
> > Any reason why the resource is checked first, not last?
> >
> > If the programmer decides to use the resource, the "locateAll" effectively
> > turns into a "locateNone". Not real
> On Oct. 5, 2014, 5:58 p.m., Christoph Feck wrote:
> > Sorry for chiming in late, just noticed the commit.
> >
> > Any reason why the resource is checked first, not last?
> >
> > If the programmer decides to use the resource, the "locateAll" effectively
> > turns into a "locateNone". Not real
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120099/
---
(Updated Oct. 5, 2014, 5:32 p.m.)
Status
--
This change has been mar
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120099/#review67966
---
Sorry for chiming in late, just noticed the commit.
Any reaso
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120099/#review67755
---
Ship it!
Sounds like a great idea to me. Apart from the small
14 matches
Mail list logo
