> On Dec. 8, 2014, 8:40 p.m., Albert Astals Cid wrote:
> > I don't think this makes sense at a framework level. If some application is
> > so special that really needs a special case, they can call setText over the
> > kaction themselves, otherwise we're going to end up havin 20 different "Add
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/121372/
---
(Updated Dec. 8, 2014, 11:41 p.m.)
Status
--
This change has been di
> On Dec. 8, 2014, 3:40 p.m., Albert Astals Cid wrote:
> > I don't think this makes sense at a framework level. If some application is
> > so special that really needs a special case, they can call setText over the
> > kaction themselves, otherwise we're going to end up havin 20 different "Add
> On des. 8, 2014, 8:40 p.m., Albert Astals Cid wrote:
> > I don't think this makes sense at a framework level. If some application is
> > so special that really needs a special case, they can call setText over the
> > kaction themselves, otherwise we're going to end up havin 20 different "Add
> On Dec. 8, 2014, 8:40 p.m., Albert Astals Cid wrote:
> > I don't think this makes sense at a framework level. If some application is
> > so special that really needs a special case, they can call setText over the
> > kaction themselves, otherwise we're going to end up havin 20 different "Add
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/121372/#review71585
---
I don't think this makes sense at a framework level. If some a
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/121372/
---
(Updated Dec. 6, 2014, 3:49 p.m.)
Review request for KDE Frameworks, Loca
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/121372/
---
Review request for KDE Frameworks, Localization and Translation (l10n) and
