From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Scott Garman <scott.a.garman@intel.com>
Subject: Re: [PATCH 0/2] sudo upgrade
Date: Wed, 29 Jun 2011 20:42:48 -0700 [thread overview]
Message-ID: <4E0BF0B8.6070307@linux.intel.com> (raw)
In-Reply-To: <cover.1308071077.git.scott.a.garman@intel.com>
On 06/14/2011 10:19 AM, Scott Garman wrote:
> Hello,
>
> Here's a recipe upgrade I squeezed in between some other things this
> morning.
>
> The following changes since commit 7aa7673459376aff911cef820c9417c998d1aa96:
>
> meta-yocto/linux-yocto: update to match the renamed linux-yocto recipes (2011-06-14 09:21:32 -0700)
>
> are available in the git repository at:
> git://git.pokylinux.org/poky-contrib sgarman/sudo-upgrade
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=sgarman/sudo-upgrade
>
> Scott Garman (2):
> sudo: upgrade to v1.8.1p2
> distro_tracking: update sudo tracking info
>
> .../conf/distro/include/distro_tracking_fields.inc | 8 +++---
> meta/recipes-extended/sudo/sudo.inc | 27 ++++++++-----------
> .../sudo/{sudo_1.7.4p6.bb => sudo_1.8.1p2.bb} | 4 +-
> 3 files changed, 17 insertions(+), 22 deletions(-)
> rename meta/recipes-extended/sudo/{sudo_1.7.4p6.bb => sudo_1.8.1p2.bb} (52%)
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
Merged into OE-Core
Thanks
Sau!
next prev parent reply other threads:[~2011-06-30 3:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 17:19 [PATCH 0/2] sudo upgrade Scott Garman
2011-06-14 17:19 ` [PATCH 1/2] sudo: upgrade to v1.8.1p2 Scott Garman
2011-06-14 17:19 ` [PATCH 2/2] distro_tracking: update sudo tracking info Scott Garman
2011-06-30 3:42 ` Saul Wold [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-24 16:32 [PATCH 0/2] sudo upgrade Scott Garman
2011-01-28 1:28 ` Saul Wold
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=4E0BF0B8.6070307@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=scott.a.garman@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 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.