On Mon, Oct 7, 2013 at 9:46 PM, Lisandro Damián Nicanor Pérez Meyer <perezme...@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.
What I want to know is that which component to push it to. > > In this specific case, please do submit it upstream and let's see what they > say (they might want some cosmetic chcomponentanges, for example). If they > ACK the > patch, I'll happily apply it on the package until it gets included in the next > release. > > Kinds regards, Lisandro. > > -- > > Lisandro Damián Nicanor Pérez Meyer > http://perezmeyer.com.ar/ > http://perezmeyer.blogspot.com/ -- YunQiang Su -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cakcpw6xgncfklmskcyzntuhjioq2n0ne8bd-fokbl1jhub6...@mail.gmail.com
