I think we have way uglier things than cherry-picks in our history tree, and
repeated commits are just a natural part of branching. Sure, we can *aim* for a
cleaner history, but let's not unnecessarily restrict ourselves to one.
In the release/rc branch approach, the final release is incremental
Just to make sure everybody understands:
With this change applied all NOTIFY properties that are currently documented
will not be documented anymore.
If there are no objections before coming Tuesday (13 March) 09:00 Oslo time I
will put this patch in.
Casper
___
> Unfortunately, after a thorough evaluation of the GSoC 2012 MOPA (Mentor
> Organization Participation Agreement), Nokia employees are not able to
> participate in this year GSoC. The details on the reasoning is unbeknownst to
> me. Sorry.
I then infer that the Qt Project won't enter this year
On 09/03/2012 10:07, ext STEFANI Mathieu wrote:
> The deadline is now in 7 hours (23:00 UTC)
>
> As a student perspective, I would really be enthusiast working on the Qt
> Project, and
> I think it definitely should be sent for approval to the GSoC 2012.
>
> However, the project needs mentors. Nok
On Fri, Mar 09, 2012 at 07:16:24PM +, ext shane.kea...@accenture.com wrote:
>
> (rc1)-o-o-o-o-o-o-fix-o-o-o-o-o-o-fix
> \
> fix(rc2)-fix(v4.8.1)
>
this is no option, because it "loses" the tag from the history.
"traditionally" we have merged back the release branch to the
maintenan
> This was discussed earlier, and we were thinking about using a branch.
> It
> was decided that we will try without. The basic idea is that at any
> time
> the code should be good to use. Naturally it is not always so, thus we
> may
> need to take another try.
>
> We have nothing against using a b
Hi,
I'm working on a QRegExp::operator QRegularExpression() implementation
so that we can remove QRegExp from public API (reducing the breakages
to a minimum -- hopefully nobody was actually using implicit
conversions for those methods, and the QRegExp constructor is
explicit). But I'm having an h
On Fri, 9 Mar 2012, laszlo.p.ag...@nokia.com wrote:
> Hi Jon,
>
> Yes, good catch, the built-in timestamping of QWindowSystemInterface is
> broken due to the lack of a call to start() or restart(). This affects mouse
> and touch events generated by plugins that do not provide their own
> timest
Hi Tuuka,
On Fri, Mar 9, 2012 at 8:16 AM, Turunen Tuukka wrote:
>
> On 9.3.2012 17.41, "Girish Ramakrishnan" wrote:
>
>
>>Hi,
>>
>>2012/3/9 Salovaara Akseli :
>>> Hi,
>>>
>>>
>>>
>>> We are currently preparing & testing Qt 4.8.1 open source release for
>>>next
>>> week. Exact release date is sti
Hi Carsten,
Yes, of course. I'll be happy about that.
When you begin?
A small remark: If you know English, then help me to correct issue Wiki on
English spelling in
https://qt-project.org/wiki/QtSerialPort
:)
Best regards,
Denis
09.03.2012, 20:05, "Carsten Breuer" :
> Hi Denis,
>
> I'm inte
On 9.3.2012 17.41, "Girish Ramakrishnan" wrote:
>Hi,
>
>2012/3/9 Salovaara Akseli :
>> Hi,
>>
>>
>>
>> We are currently preparing & testing Qt 4.8.1 open source release for
>>next
>> week. Exact release date is still open, until all tests are passed.
>>And, as
>> discussed it is possible that c
Hi,
The deadline is now in 7 hours (23:00 UTC)
As a student perspective, I would really be enthusiast working on the Qt
Project, and
I think it definitely should be sent for approval to the GSoC 2012.
However, the project needs mentors. Nokia employees seem to have been removed
from the mentors
Hi all.
I created a Wiki page for the addon QtSerialPort
https://qt-project.org/wiki/QtSerialPort
and I need help with spelling of English.
Help ме please.
Best regards,
Denis
___
Development mailing list
Development@qt-project.org
http://lists.qt-p
Hi,
2012/3/9 Salovaara Akseli :
> Hi,
>
>
>
> We are currently preparing & testing Qt 4.8.1 open source release for next
> week. Exact release date is still open, until all tests are passed. And, as
> discussed it is possible that critical problems are found, and then we need
> to take another try
>
> now the Qt4 version is not developed?
>
> and I only get the lastest version from
> git://gitorious.org/qt/qtbase.git ??
>
The Qt4 repository is still at git://gitorious.org/qt/qt.git
Bug fixes can still go there for 4.8.x patch releases.
The modular repositories (e.g. qtbase) are only for Qt5
On Thursday 08 March 2012 20:36:07 Laszlo Papp wrote:
> Hi,
>
> I would like to experiment with a command line parser in Qt
> Playground. The topic and the use case were more or less discussed
> previously on the qt5-feedback mailing list around last October.
>
> It is not a separate module, but
Hi,
We are currently preparing & testing Qt 4.8.1 open source release for next
week. Exact release date is still open, until all tests are passed. And, as
discussed it is possible that critical problems are found, and then we need to
take another try.
We are currently testing against sha1 that
On Fri, Mar 09, 2012 at 01:36:07AM +0200, ext Laszlo Papp wrote:
> It is not a separate module, but class(es). The name for this
> experiment, in playground,
>
it's entirely misguided to create a playground project for "classes"
(which are presumably meant to end up in qtcore). what you should be
r
Hi Jon,
Yes, good catch, the built-in timestamping of QWindowSystemInterface is broken
due to the lack of a call to start() or restart(). This affects mouse and touch
events generated by plugins that do not provide their own timestamps.
The patch looks good although we may want to consider swi
19 matches
Mail list logo
