Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] tar: upgrade to version 1.25
Date: Wed, 17 Nov 2010 18:18:39 -0800	[thread overview]
Message-ID: <4CE48CFF.7070406@balister.org> (raw)
In-Reply-To: <1290046421-22553-1-git-send-email-sgarman@zenlinux.com>

On 11/17/2010 06:13 PM, Scott Garman wrote:
> Signed-off-by: Scott Garman<sgarman@zenlinux.com>
> ---
>   recipes/tar/tar_1.23.bb |    6 ------
>   recipes/tar/tar_1.25.bb |    6 ++++++
>   2 files changed, 6 insertions(+), 6 deletions(-)
>   delete mode 100644 recipes/tar/tar_1.23.bb
>   create mode 100644 recipes/tar/tar_1.25.bb
>
> diff --git a/recipes/tar/tar_1.23.bb b/recipes/tar/tar_1.23.bb
> deleted file mode 100644
> index dc37247..0000000
> --- a/recipes/tar/tar_1.23.bb
> +++ /dev/null
> @@ -1,6 +0,0 @@
> -require tar.inc
> -
> -PR = "${INC_PR}"
> -
> -SRC_URI[md5sum] = "41e2ca4b924ec7860e51b43ad06cdb7e"
> -SRC_URI[sha256sum] = "c9328372db62fbb1d94c9e4e3cefc961111af46de47085b635359c00a0eebe36"
> diff --git a/recipes/tar/tar_1.25.bb b/recipes/tar/tar_1.25.bb
> new file mode 100644
> index 0000000..c611f77
> --- /dev/null
> +++ b/recipes/tar/tar_1.25.bb
> @@ -0,0 +1,6 @@
> +require tar.inc
> +
> +PR = "${INC_PR}"
> +
> +SRC_URI[md5sum] = "6e497f861c77bbba2f7da4e10270995b"
> +SRC_URI[sha256sum] = "f3f6ce41b8e0f327abd05c95990f113ddafbae131e10f79a99728ed46458494b"


Acked-by: Philip Balister <philip@balister.org>

Can you add tar-1.23 to the removal.txt file? Ask it be removed in a 
couple of months. This way we have a schedule to delete the older recipe.

Philip



  reply	other threads:[~2010-11-18  2:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18  2:13 [PATCH] tar: upgrade to version 1.25 Scott Garman
2010-11-18  2:18 ` Philip Balister [this message]
2010-11-18  2:48   ` Scott Garman
2010-11-18  2:54     ` Philip Balister
2010-11-18  3:28       ` Khem Raj
2010-11-18  8:34         ` Martin Jansa
2010-11-18 16:35           ` Scott Garman

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=4CE48CFF.7070406@balister.org \
    --to=philip@balister.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox