From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Some Upstream-Status patch updates
Date: Mon, 14 Nov 2011 17:14:53 -0800 [thread overview]
Message-ID: <cover.1321319621.git.scott.a.garman@intel.com> (raw)
Taking care of a few patch straglers that were missing Upstream-Status.
The following changes since commit f2316ff39670ed99382411e15ac035550360fbdd:
opkg: Ensure we use the uname/gname fields when extracting tarballs (2011-11-14 11:15:36 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib sgarman/upstream-status-updates
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=sgarman/upstream-status-updates
Scott Garman (2):
dosfstools: add Upstream-Status to patches
base-passwd: add Upstream-Status to patches, remove unused patch
.../base-passwd/base-passwd-3.5.22/mysql.patch | 13 ----------
.../base-passwd/base-passwd-3.5.22/nobash.patch | 25 +++++++++++--------
.../base-passwd/base-passwd-3.5.22/root-home.patch | 11 ++++++--
.../dosfstools/dosfstools/2.6.20-syscall.patch | 7 +++++
.../dosfstools/dosfstools/alignment_hack.patch | 4 +++
.../dosfstools/dosfstools-msdos_fs-types.patch | 7 +++++
.../dosfstools/include-linux-types.patch | 5 ++++
.../dosfstools/dosfstools/mkdosfs-bootcode.patch | 7 +++++
.../dosfstools/dosfstools/mkdosfs-dir.patch | 7 +++++
.../dosfstools/msdos_fat12_undefined.patch | 7 +++++
10 files changed, 66 insertions(+), 27 deletions(-)
delete mode 100644 meta/recipes-core/base-passwd/base-passwd-3.5.22/mysql.patch
--
1.7.5.4
next reply other threads:[~2011-11-15 1:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 1:14 Scott Garman [this message]
2011-11-15 1:14 ` [PATCH 1/2] dosfstools: add Upstream-Status to patches Scott Garman
2011-11-15 1:14 ` [PATCH 2/2] base-passwd: add Upstream-Status to patches, remove unused patch Scott Garman
2011-11-24 22:54 ` [PATCH 0/2] Some Upstream-Status patch updates Richard Purdie
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.1321319621.git.scott.a.garman@intel.com \
--to=scott.a.garman@intel.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox