mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Phillip Lougher <phillip@lougher.demon.co.uk>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Rob Landley <rob@landley.net>,
	linux-kernel@vger.kernel.org,
	squashfs-devel@lists.sourceforge.net
Subject: Re: Squashfs 4.0 tools
Date: Tue, 31 Mar 2009 06:51:23 +0100	[thread overview]
Message-ID: <49D1AF5B.6090006@lougher.demon.co.uk> (raw)
In-Reply-To: <20090330175524.4e8f802e@nehalam>

Stephen Hemminger wrote:
> On Sun, 29 Mar 2009 11:02:19 +0200
> Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> 
>> On Sun, Mar 29, 2009 at 00:27, Rob Landley <rob@landley.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

  reply	other threads:[~2009-03-31  5:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24  1:08 Stephen Hemminger
2009-03-24  2:39 ` Phillip Lougher
2009-03-24  5:15   ` Michael Tokarev
2009-03-31  6:01     ` [Squashfs-devel] " Phillip Lougher
2009-03-28 22:27   ` Rob Landley
2009-03-29  9:02     ` Geert Uytterhoeven
2009-03-31  0:55       ` Stephen Hemminger
2009-03-31  5:51         ` Phillip Lougher [this message]
2009-03-31 19:31         ` Rob Landley
2009-04-01  1:05           ` Phillip Lougher
2009-04-01 11:40             ` [Squashfs-devel] " Peter Korsgaard
2009-04-05 23:27             ` Phillip Lougher
2009-04-06  8:55               ` Rob Landley

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=49D1AF5B.6090006@lougher.demon.co.uk \
    --to=phillip@lougher.demon.co.uk \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    --cc=shemminger@vyatta.com \
    --cc=squashfs-devel@lists.sourceforge.net \
    /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

Powered by JetHome