From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [pull request] webkit: Version bump to 1.11.5
Date: Thu, 5 Sep 2013 11:01:43 +0200 [thread overview]
Message-ID: <20130905110143.55467e66@skate> (raw)
In-Reply-To: <CAG2jQ8g2SYnbc5eqvhMnw-5=qQXj4K2q_aW4r70MRExdYjmpjw@mail.gmail.com>
Dear Markos Chandras,
On Thu, 5 Sep 2013 09:48:32 +0100, Markos Chandras wrote:
> > A 1490 line patch is not so huge, I believe it should make it on the
> > list, and if not, Peter will validate it manually. I agree that the
> > overall patch should be sent to the list for review.
>
> Well, it's an upstream patch, so i don't think there is much to review
> there but I can send it to the list anyway.
It's not much to review this upstream patch, but rather the overall
changes in webkit.mk and so on.
> >> Is there a reason why you cannot download the upstream patches with
> >> WEBKIT_PATCH ?
> >
> > When it's possible, it's indeed a good idea.
>
> Unfortunately, I can't (or I don't think I can) use that. I had to
> tweak the upstream patches a bit,
> for example delete the changes in the ChangeLog files since they don't apply.
> For other patches, I had to merge 2-3 upstream patches into a single
> one in order to fix the problem completely instead of providing
> separate patches with 1-2 line fixes.
Ok. Since the patches are upstream, that's fine, since it means they
will be removed at some point in the future.
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-09-05 9:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 13:59 [Buildroot] [pull request] webkit: Version bump to 1.11.5 Markos Chandras
2013-09-04 16:49 ` Arnout Vandecappelle
2013-09-05 8:01 ` Thomas Petazzoni
2013-09-05 8:48 ` Markos Chandras
2013-09-05 9:01 ` Thomas Petazzoni [this message]
2013-09-05 9:15 ` Markos Chandras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130905110143.55467e66@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox