[Qt-qml] Where do the bug fixes go?

Gregory Schlomoff gregory.schlomoff at gmail.com
Fri Jul 23 13:26:51 CEST 2010


Nevermind, I just found it :
http://qt.gitorious.org/+qt-developers/qt/staging/commits/qml/4.7

greg

On Fri, Jul 23, 2010 at 6:25 PM, Gregory Schlomoff <
gregory.schlomoff at gmail.com> wrote:

> Can someone be kind enough to provide us with a link?
>
> I can't see any qt-qml branch under
> http://qt.gitorious.org/+qt-developers/qt/staging/
>
> Or maybe it is still too early, and the branch will appear later?
>
> <http://qt.gitorious.org/+qt-developers/qt/staging/>Thanks!
>
> greg
>
>
> On Fri, Jul 23, 2010 at 9:51 AM, <michael.brasser at nokia.com> wrote:
>
>> It is now being mirrored (thanks Warwick and Rohan).
>>
>> Michael
>>
>> On 23/07/2010, at 2:47 AM, ext Olivier Goffart wrote:
>>
>> > Hi,
>> >
>> > You are right,  It seems that the qt-qml branches are not mirrored in
>> the
>> > public qt-staging repository.
>> >
>> > Rohan, maybe you can fix this?
>> >
>> >
>> > On Thursday, 22. July 2010 18:30:16 ext Stephen Kelly wrote:
>> >> I can't seem to get it from there:
>> >>
>> >> kde-devel at chimera:~/kde/src/qt(4.7)$ git show
>> >> 64833c0a648211f3fe7547436f022edc0ceb51ac
>> >> fatal: bad object 64833c0a648211f3fe7547436f022edc0ceb51ac
>> >>
>> >>
>> >> kde-devel at chimera:~/kde/src/qt(4.7)$ git fetch staging
>> >> remote: Counting objects: 559, done.
>> >> remote: Compressing objects: 100% (250/250), done.
>> >> remote: Total 251 (delta 212), reused 0 (delta 0)
>> >> Receiving objects: 100% (251/251), 274.86 KiB | 366 KiB/s, done.
>> >> Resolving deltas: 100% (212/212), completed with 125 local objects.
>> >> From git://gitorious.org/+qt-developers/qt/staging
>> >>   a1a3535..4981895  multimedia/4.6 -> staging/multimedia/4.6
>> >>   3a7b706..07f1319  multimedia/4.7 -> staging/multimedia/4.7
>> >>   8669542..6b6778c  oslo-1/4.6 -> staging/oslo-1/4.6
>> >>   3fad4bd..62b2022  oslo-1/4.7 -> staging/oslo-1/4.7
>> >>   a1a3535..4981895  oslo-2/4.6 -> staging/oslo-2/4.6
>> >>   22e0ebd..c4bea74  oslo-2/4.7 -> staging/oslo-2/4.7
>> >>   df6549d..c8bb76e  oslo-2/master -> staging/oslo-2/master
>> >>   a1a3535..4981895  s60/4.6    -> staging/s60/4.6
>> >>   ebe6a52..4280c4c  s60/4.7    -> staging/s60/4.7
>> >> kde-devel at chimera:~/kde/src/qt(4.7)$ git show
>> >> 64833c0a648211f3fe7547436f022edc0ceb51ac
>> >> fatal: bad object 64833c0a648211f3fe7547436f022edc0ceb51ac
>> >> kde-devel at chimera:~/kde/src/qt(4.7)$ git remote show staging
>> >> * remote staging
>> >>  Fetch URL: git://gitorious.org/+qt-developers/qt/staging.git
>> >>  Push  URL: git://gitorious.org/+qt-developers/qt/staging.git
>> >>  HEAD branch (remote HEAD is ambiguous, may be one of the following):
>> >>    multimedia/master
>> >>    oslo-1/master
>> >>    s60/master
>> >>  Remote branches:
>> >>    berlin-1/4.6-continuous-integration tracked
>> >>    berlin-1/fake-master                tracked
>> >>    doc-1/4.5                           tracked
>> >>    doc-1/4.6                           tracked
>> >>    doc-1/4.6-stable                    tracked
>> >>    doc-1/master                        tracked
>> >>    doc-1/master-stable                 tracked
>> >>    multimedia/4.5                      tracked
>> >>    multimedia/4.6                      tracked
>> >>    multimedia/4.6-stable               tracked
>> >>    multimedia/4.7                      tracked
>> >>    multimedia/master                   tracked
>> >>    multimedia/master-stable            tracked
>> >>    oslo-1/4.6                          tracked
>> >>    oslo-1/4.6-continuous-integration   tracked
>> >>    oslo-1/4.6-stable                   tracked
>> >>    oslo-1/4.7                          tracked
>> >>    oslo-1/4.7-cutoff                   tracked
>> >>    oslo-1/master                       tracked
>> >>    oslo-1/master-stable                tracked
>> >>    oslo-1/os1-4.7                      tracked
>> >>    oslo-2/4.6                          tracked
>> >>    oslo-2/4.6-continuous-integration   tracked
>> >>    oslo-2/4.6-stable                   tracked
>> >>    oslo-2/4.7                          tracked
>> >>    oslo-2/master                       tracked
>> >>    s60/4.6                             tracked
>> >>    s60/4.6-continuous-integration      tracked
>> >>    s60/4.7                             tracked
>> >>    s60/4.8                             tracked
>> >>    s60/ConnectivityCamp                tracked
>> >>    s60/DocUpdatesForSymbian            tracked
>> >>    s60/NetworkCleanup                  tracked
>> >>    s60/SymbianFilePerf                 tracked
>> >>    s60/armv6-atomics                   tracked
>> >>    s60/gcce-fixes                      tracked
>> >>    s60/linkingFixes                    tracked
>> >>    s60/master                          tracked
>> >>    s60/mmfphonon                       tracked
>> >>    s60/multimedia-audio                tracked
>> >>    s60/native-fileengine               tracked
>> >>    s60/nativeresolver                  tracked
>> >>    s60/new-symbian-allocator           tracked
>> >>    s60/no-tmp-dirs                     tracked
>> >>    s60/s60-mkspec-docs                 tracked
>> >>    s60/s60-webkit-stuff                tracked
>> >>    s60/s60_webkit_experimental         tracked
>> >>    s60/static-linkage                  tracked
>> >>    s60/translucent-overlay             tracked
>> >>    s60/windowGroups                    tracked
>> >> kde-devel at chimera:~/kde/src/qt(4.7)$
>> >>
>> >> On 7/22/10, Olivier Goffart <olivier.goffart at nokia.com> wrote:
>> >>> On Thursday, 22. July 2010 17:02:28 ext Stephen Kelly wrote:
>> >>>> Hi,
>> >>>>
>> >>>> I'm looking for the patch which fixes this bug:
>> >>>>
>> >>>> http://bugreports.qt.nokia.com/browse/QTBUG-12295
>> >>>>
>> >>>> As I just submitted a minimal test case I need to test the fix with
>> my
>> >>>> actual code to see if the problem is fixed or if there's another bug
>> >>>> which will make my component fail.
>> >>>>
>> >>>> The commit referenced in the bug is not in the official qt repo yet.
>> >>>> Alan mentioned at Akademy the existence of a another qt clone where
>> >>>> qml people commit fixes to which are later merged into official at
>> >>>> some point (if there are no blocker commits). That took about an hour
>> >>>> of debugging time for myself and Alan. I've also seen mention of a
>> >>>> qt-qml repo on this mailing list.
>> >>>>
>> >>>> Where is the qt-qml repo? How can I get and test the patch?
>> >>>
>> >>> It is still in the staging:
>> >>> http://qt.gitorious.org/+qt-developers/qt/staging/
>> >>>
>> >>> Commit in Qt are first pushed in a staging branch, and get to the main
>> >>> repository only if there is no failures in that branch
>> > _______________________________________________
>> > Qt-qml mailing list
>> > Qt-qml at trolltech.com
>> > http://lists.trolltech.com/mailman/listinfo/qt-qml
>>
>>
>> _______________________________________________
>> Qt-qml mailing list
>> Qt-qml at trolltech.com
>> http://lists.trolltech.com/mailman/listinfo/qt-qml
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt.nokia.com/pipermail/qt-qml/attachments/20100723/4ab0e29c/attachment.html 


More information about the Qt-qml mailing list