From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-gnome][PATCH 0/2] Remove some recipes that are in OE-Core (cover letter only)
Date: Tue, 16 Apr 2013 14:46:48 +0100 [thread overview]
Message-ID: <cover.1366119759.git.paul.eggleton@linux.intel.com> (raw)
In case you're wondering why I've only sent the cover letter for just two
patches, I tried sending them as normal and what I got was:
fatal: pull-29844/0001-hicolor-icon-theme-remove.patch: 29: patch contains a line longer than 998 characters
warning: no patches were sent
They are just deletes though so they don't contain much in the way of
substance.
The following changes since commit a45830a39bb47a9eab27980d52966226c9504ea4:
recipes: Unify indentation (2013-04-15 16:23:17 +0200)
are available in the git repository at:
git://git.openembedded.org/meta-openembedded-contrib paule/meta-gnome
http://cgit.openembedded.org/cgit.cgi/meta-openembedded-contrib/log/?h=paule/meta-gnome
Paul Eggleton (2):
hicolor-icon-theme: remove
libical: remove
.../hicolor-icon-theme/files/index.theme | 1731 --------------------
.../hicolor-icon-theme/hicolor-icon-theme_0.12.bb | 23 -
.../libical/files/pthread-fix.patch | 52 -
meta-gnome/recipes-support/libical/libical_0.48.bb | 17 -
4 files changed, 1823 deletions(-)
delete mode 100644 meta-gnome/recipes-gnome/hicolor-icon-theme/files/index.theme
delete mode 100644 meta-gnome/recipes-gnome/hicolor-icon-theme/hicolor-icon-theme_0.12.bb
delete mode 100644 meta-gnome/recipes-support/libical/files/pthread-fix.patch
delete mode 100644 meta-gnome/recipes-support/libical/libical_0.48.bb
--
1.7.10.4
next reply other threads:[~2013-04-16 14:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 13:46 Paul Eggleton [this message]
2013-04-16 14:05 ` [meta-gnome][PATCH 0/2] Remove some recipes that are in OE-Core (cover letter only) Martin Jansa
2013-04-16 14:11 ` Paul Eggleton
2013-04-16 14:34 ` Martin Jansa
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=cover.1366119759.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.