All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <saul.wold@intel.com>
To: Jingdong Lu <jingdong.lu@windriver.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 0/4] [PULL] Add some new packages and rename	liburi-perl.
Date: Tue, 25 Jan 2011 18:51:23 -0800	[thread overview]
Message-ID: <4D3F8C2B.5060506@intel.com> (raw)
In-Reply-To: <cover.1295601800.git.jingdong.lu@windriver.com>

On 01/21/2011 01:26 AM, Jingdong Lu wrote:
> Add mailx, cups, msmtp.
> Rename liburi-perl_1.56 to liburi-perl_1.56.bb
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
>    Branch: jingdonglu/distro
>    Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=jingdonglu/distro
>
> Thanks,
>      Jingdong Lu<jingdong.lu@windriver.com>
> ---
>
>
> Jingdong Lu (4):
>    mailx: Add mailx
>    cups: Add cups
>    msmtp: Add msmtp
>    liburi-perl: Rename liburi-perl

Hi Jingdong,

I did not pull mailx, cups or msmtp for various failures and needed to 
get more history about where these recipes and patches came from.  Did 
you use OpenEmbedded as a reference for these, if so, you need to credit 
OE and document where any why the patches are needed for cups.

We also held off from the lsb task, since it contained all of these.

If you have any questions, let me know.


Sau!


>
>   .../perl/{liburi-perl_1.56 =>  liburi-perl_1.56.bb} |    0
>   .../cups/cups-1.4.4/configure.patch                |  117 ++++++++++++++++++++
>   .../cups/cups-1.4.4/skip_tools.patch               |   51 +++++++++
>   .../cups/cups-1.4.4/use_echo_only_in_init.patch    |   11 ++
>   meta/recipes-extended/cups/cups14.inc              |   86 ++++++++++++++
>   meta/recipes-extended/cups/cups_1.4.4.bb           |   17 +++
>   meta/recipes-extended/mailx/mailx_12.4.bb          |   23 ++++
>   meta/recipes-extended/msmtp/msmtp_1.4.21.bb        |   31 +++++
>   8 files changed, 336 insertions(+), 0 deletions(-)
>   rename meta/recipes-devtools/perl/{liburi-perl_1.56 =>  liburi-perl_1.56.bb} (100%)
>   create mode 100644 meta/recipes-extended/cups/cups-1.4.4/configure.patch
>   create mode 100644 meta/recipes-extended/cups/cups-1.4.4/skip_tools.patch
>   create mode 100644 meta/recipes-extended/cups/cups-1.4.4/use_echo_only_in_init.patch
>   create mode 100644 meta/recipes-extended/cups/cups14.inc
>   create mode 100644 meta/recipes-extended/cups/cups_1.4.4.bb
>   create mode 100644 meta/recipes-extended/mailx/mailx_12.4.bb
>   create mode 100644 meta/recipes-extended/msmtp/msmtp_1.4.21.bb
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>



      parent reply	other threads:[~2011-01-26  2:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21  9:26 [PATCH 0/4] [PULL] Add some new packages and rename liburi-perl Jingdong Lu
2011-01-21  9:26 ` [PATCH 1/4] mailx: Add mailx Jingdong Lu
2011-01-21  9:26 ` [PATCH 2/4] cups: Add cups Jingdong Lu
2011-01-21  9:26 ` [PATCH 3/4] msmtp: Add msmtp Jingdong Lu
2011-01-21  9:26 ` [PATCH 4/4] liburi-perl: Rename liburi-perl Jingdong Lu
2011-01-26  2:51 ` Saul Wold [this message]

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=4D3F8C2B.5060506@intel.com \
    --to=saul.wold@intel.com \
    --cc=jingdong.lu@windriver.com \
    --cc=poky@yoctoproject.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.