o, then please clean it up before pushing.
Yes, I realised after the fact that I had created one of these so
sorry about that. I've already now switched to using --rebase. If one
does accidentally create one of these merge commits, how can they fix
it before they push?
--
Matt Williams
http://milliams.com
other area's within KDE, which I hope one day will
> not be the case.
>
> And before you ask, yes, I very much would like a 'astyle' run on all the
> code in kdelibs to settle this once and for all.
And then how about a .kateconfig file
(http://kate-editor.org/2006/02/09/kateconfig-files/) to help
'enforce' this?
--
Matt Williams
http://milliams.com
"addons", "platform".
> Once we have this (I would estimate something like a year of work), we may
> start to try to get some of the enhancements into Qt.
> And if it doesn't get accepted then, still no problem, since by then it will
> have the form of a smallish library with very few or no dependencies beside
> the Qt libs.
Absolutely. I think that this is the most sensible and practical
approach to take.
--
Matt Williams
http://milliams.com
On 31 October 2010 12:37, Modestas Vainius wrote:
> Hello,
>
> On sekmadienis 31 Spalis 2010 14:04:28 Matt Williams wrote:
>> On 31 October 2010 11:53, John Tapsell wrote:
>> > On 31 October 2010 11:33, Mark Kretschmann wrote:
>> >> Hey all,
>> &g
omments on this move. It would be nice that you could also work on the
> klickety-ksame mode.
>
> I found that Matt Williams is the current module coordinator according to
> http://techbase.kde.org/Projects/Release_Team
> so matt, please review both klickety and ksame and determine whe
wrapper classes in
KDE? So I guess we can't just jump and do this for KDE 4.6 -- it's
going to force us into taking some very big steps like jumping to KDE5
or at least boosting the soversion of the libs.
--
Matt Williams
http://milliams.com
