Openembedded Core Discussions
 help / color / mirror / Atom feed
From: alexander.kanavin@linux.intel.com
To: "Paul Eggleton" <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 11/21] webkitgtk: add a new recipe for latest upstream version
Date: Thu, 30 Jul 2015 22:02:54 +0300 (EEST)	[thread overview]
Message-ID: <57131.10.252.34.83.1438282974.squirrel@linux.intel.com> (raw)
In-Reply-To: <3191513.j5SDqNSYIE@peggleto-mobl.ger.corp.intel.com>

> I have to say I think it would be simpler not to rename it, FWIW...

Why? Not renaming the recipe buys you nothing; the new webkit has a new
API, so for anyone out there using the old webkit things will break
regardless of whether the recipe has been renamed or not.


Alex





  reply	other threads:[~2015-07-30 19:03 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-30 14:27 [PATCH 00/21] Update webkitgtk to latest stable upstream; replace midori with epiphany Alexander Kanavin
2015-07-30 14:27 ` [PATCH 01/21] classes/gnomebase: change tarball compression to xz Alexander Kanavin
2015-07-30 14:27 ` [PATCH 02/21] harfbuzz: enable icu feature Alexander Kanavin
2015-07-30 14:27 ` [PATCH 03/21] classes/cmake: add arch conversion routine Alexander Kanavin
2015-07-30 14:27 ` [PATCH 04/21] jpeg: update to version 9a Alexander Kanavin
2015-07-30 14:27 ` [PATCH 05/21] libnotify: update to version 0.7.6 Alexander Kanavin
2015-07-30 14:27 ` [PATCH 06/21] giflib: add a recipe from meta-oe Alexander Kanavin
2015-07-30 14:27 ` [PATCH 07/21] libyaml: " Alexander Kanavin
2015-07-30 14:27 ` [PATCH 08/21] ruby: add a recipe from meta-ruby Alexander Kanavin
2015-07-30 14:27 ` [PATCH 09/21] libsecret: add a recipe from meta-gnome Alexander Kanavin
2015-07-30 14:27 ` [PATCH 10/21] libwebp: add a recipe from meta-oe Alexander Kanavin
2015-07-30 14:27 ` [PATCH 11/21] webkitgtk: add a new recipe for latest upstream version Alexander Kanavin
2015-07-30 14:43   ` Martin Jansa
2015-07-30 15:30     ` Alexander Kanavin
2015-07-30 17:57       ` Paul Eggleton
2015-07-30 19:02         ` alexander.kanavin [this message]
2015-07-30 18:54       ` alexander.kanavin
2015-07-30 14:27 ` [PATCH 12/21] p11-kit: add a recipe from meta-oe Alexander Kanavin
2015-07-30 14:27 ` [PATCH 13/21] gcr: add a recipe from meta-gnome Alexander Kanavin
2015-07-30 14:27 ` [PATCH 14/21] iso-codes: add a recipe from meta-oe Alexander Kanavin
2015-07-30 14:27 ` [PATCH 15/21] libwnck3: add a recipe from meta-gnome Alexander Kanavin
2015-07-30 14:27 ` [PATCH 16/21] gnome-desktop3: " Alexander Kanavin
2015-07-30 14:27 ` [PATCH 17/21] glib: add a warning suppression patch to glib Alexander Kanavin
2015-07-30 14:27 ` [PATCH 18/21] gsettings-desktop-schemas: add a recipe from meta-gnome Alexander Kanavin
2015-07-30 14:27 ` [PATCH 19/21] epiphany: " Alexander Kanavin
2015-08-07  4:28   ` Randy MacLeod
2015-08-07 12:44     ` Alexander Kanavin
2015-08-11 23:49       ` Randy MacLeod
2015-08-12  1:45     ` Khem Raj
2015-07-30 14:27 ` [PATCH 20/21] webkit-gtk: remove the recipe for the obsolete version 1.8.3 Alexander Kanavin
2015-07-30 14:27 ` [PATCH 21/21] midori: remove the recipe and replace references to midori with epiphany Alexander Kanavin

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=57131.10.252.34.83.1438282974.squirrel@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /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