[Development] requesting an own 4.8-blackberry10 branch on gitorious

Peter Hartmann phartmann at rim.com
Tue Dec 18 16:06:31 CET 2012

On 12/18/2012 12:05 PM, Sean Harmer wrote:
> (...)
>> In case we decide to proceed with creation of a vendor branch, is it
>> planned to be a temporary solution or something permanent?

some months ago, I was confident that this would be something temporary; 
unfortunately, practice has shown that so far we always had a few 
commits (1-10) that we needed to "short-circuit" into our branch because 
some internal team needed a commit urgently (maybe people that have 
worked on the N9 remember that situation). So I don't expect that branch 
to go away anytime soon, to be honest.

> I suppose that entirely depends upon what gets committed there. The general
> idea is to keep this branch as the minimum set of patches needed for this
> platform that cannot be merged into the Qt mainline. Peter already mentioned
> one such patch.

Yes, this is another reason why the branch will most likely not become 


> The case of expediting patches in this branch is to allow this to happen in
> the open in the spirit of the Qt project. Wherever possible the idea is to
> upstream the patches into the Qt mainline so that the vendor branch remains as
> close as possible to the official Qt Project version.
> Vladimir and Peter may have more to add of course.
> All the best,
> Sean
> --
> Dr Sean Harmer | sean.harmer at kdab.com | Senior Software Engineer
> Klarälvdalens Datakonsult AB, a KDAB Group company
> Tel. Sweden (HQ) +46-563-540090, USA +1-866-777-KDAB(5322)
> KDAB - Qt Experts - Platform-independent software solutions
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development

This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

More information about the Development mailing list