On Tuesday 08 October 2013 13:58:43 YunQiang Su wrote: > On Mon, Oct 7, 2013 at 9:46 PM, Lisandro Damián Nicanor Pérez Meyer > > <perezmeyer@gmail.com> wrote: > > On Monday 07 October 2013 09:32:12 YunQiang Su wrote: > >> Package: qtwebkit > >> Version: 2.2.1-6 > >> > >> On mips64el, qtwebkit has the same problem like qt4. > >> The attachment is the patch. > >> > >> Or where should I apply it to upstream? > > > > Hi YunQiang! As a rule of thumb, if it's something that does not involve > > packaging, pushing the patchs upstream is normally the best idea. An > > exception could be a patch that introduces something that is very > > Debian-related, but most of the time this can also be pushed upstream > > somehow. > > Thanks, I see. > I am wondering about which component should it involve to qt? > I have pushed this patch to qt/qt4/qtscripts. If the problem is in qtwebkit, then push it to qtwebkit. If in doubt, join upstream's irc #qt on freenode and ask. Kinds regards, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
Attachment:
signature.asc
Description: This is a digitally signed message part.