All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] squashfs-tools: upgrade to newer revision from git
Date: Fri, 10 Jul 2015 13:06:22 +0200	[thread overview]
Message-ID: <20150710110622.GC2397@jama> (raw)
In-Reply-To: <559F92B3.8040407@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 964 bytes --]

On Fri, Jul 10, 2015 at 12:38:59PM +0300, Alexander Kanavin wrote:
> On 07/01/2015 04:23 PM, Martin Jansa wrote:
> > On Mon, Jun 08, 2015 at 02:13:48PM +0200, Martin Jansa wrote:
> >> * 4.3 release has nasty hard to reproduce bug in LZO compression
> >>    which in few cases results in one of these 2 errors:
>  >> ....
> >>    the official repo is:
> >>    https://git.kernel.org/cgit/fs/squashfs/squashfs-tools.git
> >>    but author's github is kept in sync so we can use just that
> >
> > Ping
> 
> The author doesn't provide version tags in either of his repositories, 
> which make upstream version check impossible.
> 
> When a new version with this fix is released we should revert back to 
> tarballs. If the patch didn't already appear in poky, I would suggest 
> you cherry-pick those fixes instead.

He said that there won't be any new release in near future if ever.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2015-07-10 11:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-08 12:13 [PATCH] squashfs-tools: upgrade to newer revision from git Martin Jansa
2015-07-01 13:23 ` Martin Jansa
2015-07-10  9:38   ` Alexander Kanavin
2015-07-10 11:06     ` Martin Jansa [this message]
2015-07-10 11:31       ` Alexander Kanavin

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=20150710110622.GC2397@jama \
    --to=martin.jansa@gmail.com \
    --cc=alexander.kanavin@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 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.