[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49D1AF5B.6090006@lougher.demon.co.uk>
Date: Tue, 31 Mar 2009 06:51:23 +0100
From: Phillip Lougher <phillip@...gher.demon.co.uk>
To: Stephen Hemminger <shemminger@...tta.com>
CC: Geert Uytterhoeven <geert@...ux-m68k.org>,
Rob Landley <rob@...dley.net>, linux-kernel@...r.kernel.org,
squashfs-devel@...ts.sourceforge.net
Subject: Re: Squashfs 4.0 tools
Stephen Hemminger wrote:
> On Sun, 29 Mar 2009 11:02:19 +0200
> Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
>
>> On Sun, Mar 29, 2009 at 00:27, Rob Landley <rob@...dley.net> wrote:
>>> P.S I notice a squashfs-devel mailing list cc'd here, but there's no link to
>>> it from the squashfs.org page. Buried in the middle of a lot of text is a
>>> link to the sourceforge squashfs project page, which has a link to "forums"
>>> which are not the same as mailing lists.
>> There should be a link to it somewhere on the SF project page...
>>
>>> But it might be nice to at least _hint_ about its existence on the web page.
>>> The main page's "contact" section is your personal email and nothing else...
Squashfs is a sourceforge project, and it has a link to the main sourceforge
page from the webpage. I've always thought that sufficient because users
can get to the mailing lists, web forum, bug tracker etc. from that, and then
choose what they think is the most appropriate way to report issues.
Missing information is simply that, and I rely on feedback from users to
say if I've forgotten to add important or relevant information anywhere.
It would be helpful if that feedback didn't include an implied
criticism, that way we'll all get along better.
>
> I built it from cvs (imported into git), and it works okay.
>
Good, this is what I suggested you do :-) CVS contains everything I've
been working on for the last couple of months.
I intended to do a release last week, but, release testing found a number
of bugs and other issues which had to be addressed, and which consequently
delayed the release.
If you grabbed the tools from CVS more than a day ago you'll find
there's problems with Unsquashfs and big-endian systems. The last
bug fix (a deadlock issue in mksquashfs undiscovered since 3.4)
went in just now, and so CVS should be what's in the release.
BTW Stephen, it would be helpful if you subscribed to the
squashfs-devel mailing list, at the moment I've having to
authorise all your posts which is a bit of a pain.
Phillip
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists