Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] Add pigz as gzip-native alternative.
Date: Tue, 13 Mar 2012 15:05:31 +0000	[thread overview]
Message-ID: <2142033.FIQWIVi2oI@helios> (raw)
In-Reply-To: <1331650371-6055-1-git-send-email-bjst@enea.com>

Hi Björn,

On Tuesday 13 March 2012 15:52:51 Björn Stenberg wrote:
> pigz, which stands for parallel implementation of gzip, is a fully
> functional replacement for gzip that exploits multiple processors and
> multiple cores to the hilt when compressing data. pigz was written by Mark
> Adler, and uses the zlib and pthread libraries.
> 
> This recipe adds pigz as an alternative provider of gzip-native. Pigz is
> much faster than gzip on multi-core machines.
> 
> Upstream-status: Pending

This needs to be moved to the inner ldflags.patch, and..

> Signed-off-by: Björn Stenberg <bjst@enea.com>

this should be copied to there. The patch should also start with an 
explanation of what the patch does (in this case it's trivial, but still worth 
having in there.)

Thanks,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2012-03-13 15:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13 14:52 [PATCH] Add pigz as gzip-native alternative Björn Stenberg
2012-03-13 15:05 ` Paul Eggleton [this message]
2012-03-14 15:59   ` Björn Stenberg
2012-03-14 16:27     ` Paul Eggleton
2012-03-15  8:25       ` Björn Stenberg
2012-03-19 14:46         ` Koen Kooi
2012-03-19 15:58           ` Björn Stenberg
2012-03-19 17:56             ` Koen Kooi
2012-03-20 14:12               ` Björn Stenberg
2012-03-20 14:16                 ` Koen Kooi
2012-03-21 14:29                   ` [PATCH] pigz: Add update-altneratives support since this otherwise conflicts with busybox/gzip Richard Purdie
2012-03-19 16:32 ` [PATCH] Add pigz as gzip-native alternative 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=2142033.FIQWIVi2oI@helios \
    --to=paul.eggleton@linux.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