On 21/12/2011, at 6:16 PM, Alan Alpert wrote:
> On Wed, 21 Dec 2011 16:52:54 ext craig.sc...@csiro.au wrote:
>> On 21/12/2011, at 5:14 PM, Robin Burchell wrote:
>>> On Wed, Dec 21, 2011 at 2:57 AM, wrote:
On 21/12/2011, at 12:19 PM,
> wrote:
> Posting patches to the JIRA bugreportin
> -Original Message-
> From: development-bounces+kai.koehne=nokia@qt-project.org
> [mailto:development-bounces+kai.koehne=nokia@qt-project.org] On
> Behalf Of ext Robin Burchell
> Sent: Wednesday, December 21, 2011 7:32 AM
> To: Dave Mateer
> Cc: development@qt-project.org
> Subjec
On Wed, 21 Dec 2011 16:52:54 ext craig.sc...@csiro.au wrote:
> On 21/12/2011, at 5:14 PM, Robin Burchell wrote:
> > On Wed, Dec 21, 2011 at 2:57 AM, wrote:
> >> On 21/12/2011, at 12:19 PM,
wrote:
> >>> Posting patches to the JIRA bugreporting system is contrary to the
> >>> terms of use for th
On 21/12/2011, at 5:14 PM, Robin Burchell wrote:
> On Wed, Dec 21, 2011 at 2:57 AM, wrote:
>>
>> On 21/12/2011, at 12:19 PM,
>> wrote:
>>
>>> Posting patches to the JIRA bugreporting system is contrary to the terms of
>>> use for that system.
>>> https://bugreports.qt.nokia.com/secure/Ter
hi,
On Tue, Dec 20, 2011 at 8:59 PM, Dave Mateer wrote:
> I configured using:
>
> ./configure -developer-build -prefix "." -debug -nomake examples
> -nomake tests -no-webkit
i've not built on OS X for ages, but that -prefix looks possibly wrong
to me. qt5/README[1] says:
./configure -prefix
Hi,
I've submitted two changes last night:
- http://codereview.qt-project.org/#change,11562 - deprecating
qMalloc/qFree/qRealloc
- http://codereview.qt-project.org/#change,11563 - removing all uses
of them from QtBase
My justification for this change is pretty simple - the only real
reason to hav
On Wed, Dec 21, 2011 at 2:57 AM, wrote:
>
> On 21/12/2011, at 12:19 PM, wrote:
>
>> Posting patches to the JIRA bugreporting system is contrary to the terms of
>> use for that system.
>> https://bugreports.qt.nokia.com/secure/TermsAndConditions.html
>> Don't do this.
>
> I know I'll probably b
On 21/12/2011, at 12:19 PM, wrote:
> Posting patches to the JIRA bugreporting system is contrary to the terms of
> use for that system.
> https://bugreports.qt.nokia.com/secure/TermsAndConditions.html
> Don't do this.
I know I'll probably be shot down immediately, but.
This is one of the
Posting patches to the JIRA bugreporting system is contrary to the terms of use
for that system.
https://bugreports.qt.nokia.com/secure/TermsAndConditions.html
Don't do this.
-Original Message-
From: development-bounces+mark.keir=nokia@qt-project.org
[mailto:development-bounces+mark.
I'm attempting to build Qt5 on Mac OS X 10.6.8 to submit some patches.
I am following the instructions on the "Building Qt 5 from Git" page,
but am getting stuck on a build error.
I configured using:
./configure -developer-build -prefix "." -debug -nomake examples
-nomake tests -no-webkit
He
On Tuesday, 20 de December de 2011 15.57.21, Robin Burchell wrote:
> On Tue, Dec 20, 2011 at 3:54 PM, Harald Fernengel
>
> wrote:
> > I thought about optimizing ::fromUtf8, but since we need to iterate
> > character by character to convert the char* to utf16, the length of the
> > string should be
On Tue, Dec 20, 2011 at 3:54 PM, Harald Fernengel
wrote:
> I thought about optimizing ::fromUtf8, but since we need to iterate character
> by character to convert the char* to utf16, the length of the string should be
> rather irrelevant?
having the length would at least allow you to semi-sensibl
Hi,
On Tuesday 20 December 2011 15:41:46 ext Thiago Macieira wrote:
> On Tuesday, 20 de December de 2011 13.37.54, harald.fernen...@nokia.com
wrote:
> > Hi,
> >
> > > The difference is that QLatin1String will make an inline call to
> > > strlen(latin1data), which the compiler may be able to opti
Hi,
On Tuesday 20 December 2011 13:17:20 ext Thiago Macieira wrote:
> The difference is that QLatin1String will make an inline call to
> strlen(latin1data), which the compiler may be able to optimise. Then again,
> we could make the same in QString::fromLatin1... any takers?
http://codereview.qt-
On Tuesday, 20 de December de 2011 15.22.13, David Faure wrote:
> On Tuesday 20 December 2011 11:18:21 lars.kn...@nokia.com wrote:
> > To some extent Linux distributions have always done that as well, and I
> > still remember something called qt-copy in KDEŠ ;-)
>
> I see no relation at all. qt-cop
On Tuesday, 20 de December de 2011 13.37.54, harald.fernen...@nokia.com wrote:
> Hi,
>
> > The difference is that QLatin1String will make an inline call to
> > strlen(latin1data), which the compiler may be able to optimise. Then
> > again, we could make the same in QString::fromLatin1... any takers
On Tuesday 20 December 2011 11:18:21 lars.kn...@nokia.com wrote:
> On 12/16/11 8:37 PM, "ext David Faure" wrote:
> >On Thursday 15 December 2011 11:21:41 Turunen Tuukka wrote:
> >> So now there is total of 108 improvements and bug fixes available in Qt
> >> Commercial 4.8.0 that are not part of th
On Monday, December 12, 2011 10:30:31 you wrote:
> Stephen Kelly said:
> > On Wednesday, November 09, 2011 13:54:37 Thiago Macieira wrote:
> > > On Friday, 28 de October de 2011 12:38:38 lars.kn...@nokia.com wrote:
> > > > We've been moving this lib quite a bit already. If we move it
> > > > again,
>> Could someone please explain what the above statement means and perhaps just
>> include the git command I need to run to fulfill the requirement?
>
> To add remotes, you want something like:
> git remote add nameofremote gitrepourl
> for instance,
> git remote add github_backup g...@github.com
Hi Dave,
Welcome! Enjoy your stay. :)
On Tue, Dec 20, 2011 at 2:59 PM, Dave Mateer wrote:
> I have absolutely no idea what that means. I looked through the git manual and
> think I see how to create a remote, but I am not sure what to put as the
> target. I do not see any Qt4 project on the code
On Tuesday 20 December 2011 08:59:25 Dave Mateer wrote:
> I have several patches to Qt4 that I have posted on the bug tracker. Now
> that the new contribution model is in place, I wanted to submit those as
> patches. I'm not very familiar with git (we use SVN), and am having trouble
> at the follow
I have several patches to Qt4 that I have posted on the bug tracker. Now that
the new contribution model is in place, I wanted to submit those as patches.
I'm not very familiar with git (we use SVN), and am having trouble at the
following step on the "Qt Contributions Guidelines" page:
> Qt 4: A
Hi,
> The difference is that QLatin1String will make an inline call to
> strlen(latin1data), which the compiler may be able to optimise. Then again, we
> could make the same in QString::fromLatin1... any takers?
review?
http://codereview.qt-project.org/#change,11530
Harald
_
On Thursday, December 15, 2011 06:40:35 lars.kn...@nokia.com wrote:
> Hi everybody,
>
> sorry for not answering earlier. I actually wanted to bring the topic up
> myself, but just didn't get it out so far. I've simply been traveling a
> bit too much (I'm currently in Tokyo for the local Qt Develop
On 12/20/2011 06:10 AM, ext Sergio Ahumada wrote:
>> Unfortunately moving it into gerrit is not as easy as one might think as
>> the testing infrastructure is somewhat different between Qt 4.x and Qt 5.
>> We could move Qt 4.x into gerrit very fast, but would loose the CI on it.
>> If we want to ke
On Monday, 19 de December de 2011 23.08.11, Mathias Hasselmann wrote:
> +1 - QLatin1String is painful to use: You cannot really store references
> to it, you constantly get trouble from C++ not being able to resolve
> which of its cast operators shall be used (QString vs. QLatin1String).
> Also I n
>> So anyway, the summary of my thoughts on solving this would be:
>> - get 4.x into Gitorious ASAP
>> - get the changes into 4.x (can probably be ongoing while the above
>> isn't finished, but will be helped)
>> - cherry-pick them into Qt 5 (in any way possible) to make sure work
>> isn't lost or
On Tuesday 20 December 2011 12:25:32 ext lars.kn...@nokia.com wrote:
> Unfortunately moving it into gerrit is not as easy as one might think as
> the testing infrastructure is somewhat different between Qt 4.x and Qt 5.
> We could move Qt 4.x into gerrit very fast, but would loose the CI on it.
Lo
On 20.12.2011 13.25, "lars.kn...@nokia.com" wrote:
>On 12/16/11 6:16 AM, "ext Robin Burchell" wrote:
>
>>Hi Tuukka,
>>
>>(now that I've left some hours to digest this...)
>>
>>2011/12/15 Turunen Tuukka :
>>> So now there is total of 108 improvements and bug fixes available in Qt
>>> Commercia
On 12/16/11 8:48 PM, "ext Thiago Macieira"
wrote:
>On Friday, 16 de December de 2011 11.07.03, Sergio Ahumada wrote:
>> One idea is to have an automated process that propose the changes to
>> be merged from Qt 4.(x-1) to Qt 4.x in Gerrit as a patch (in the likes
>> of what has been done to update
On 12/16/11 6:16 AM, "ext Robin Burchell" wrote:
>Hi Tuukka,
>
>(now that I've left some hours to digest this...)
>
>2011/12/15 Turunen Tuukka :
>> So now there is total of 108 improvements and bug fixes available in Qt
>> Commercial 4.8.0 that are not part of the LGPL release. I want to
>>underl
On 12/15/11 9:23 PM, "ext Olivier Goffart" wrote:
>On Thursday 15 December 2011 11:53:12 sinan.tanil...@nokia.com wrote:
>> Hi,
>>
>> Thank you for you summary Tuukka.
>>
>> We hope to move Qt 4 to Gerrit soon. This should enable faster handling
>>of
>> contributions.
>
>Wasn't the policy to fi
On 12/16/11 8:37 PM, "ext David Faure" wrote:
>On Thursday 15 December 2011 11:21:41 Turunen Tuukka wrote:
>> So now there is total of 108 improvements and bug fixes available in Qt
>> Commercial 4.8.0 that are not part of the LGPL release.
>
>While I understand the reasons, I want to state that
> From: Thiago Macieira
> On Monday, 19 de December de 2011 09.40.44, David Faure wrote:
> > > What should this do for something like 4.8.0c? Better to not confuse
> > > things
> > > and to leave the version number as it was. In practice, I'd be surprised
> > > if
> > > there was much confusion ca
Great, that's good to hear. I think I've seen it in some other places in
the former Qt Mobility modules as well though.
Cheers,
Lars
On 12/19/11 11:42 PM, "Zhu Xizhi (Nokia-MP/Tampere)"
wrote:
>Hi,
>
>We're actually removing the usage of QLatin1Constant in QtContacts,
>QtOrganizer, and QtVersit
35 matches
Mail list logo
