All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@sunsite.dk>
To: dedekind1@gmail.com
Cc: H Hartley Sweeten <hartleys@visionengravers.com>,
	linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: Latest mkfs.jffs2 is broken.
Date: Mon, 18 Oct 2010 22:51:48 +0200	[thread overview]
Message-ID: <871v7n442j.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1287244167.1781.2.camel@brekeke> (Artem Bityutskiy's message of "Sat, 16 Oct 2010 18:49:27 +0300")

>>>>> "Artem" == Artem Bityutskiy <dedekind1@gmail.com> writes:

 Artem> On Fri, 2010-10-15 at 10:52 +0200, Peter Korsgaard wrote:
 >> >>>>> "Artem" == Artem Bityutskiy <dedekind1@gmail.com> writes:
 >> 
 >> >> Artem: Time for a v1.4.1 release?
 >> 
 Artem> Thanks. If it works, I'll back-port Mike's patch to 1.4.0 and tag it as
 Artem> 1.4.1. So 1.4.1 won't include tons of irrelevant commits.
 >> 
 >> Great. An easy way to test:

 Artem> Done. You can find v1.4.1 tag, tarball, and announcement in the "news"
 Artem> section of the web site.

Thanks, but the 1.4.1 tarball is screwed - It contains a bunch of build
files which breaks the build if they aren't removed first.

diff -urpN mtd-utils-1.4.?|diffstat
 compr_zlib.c                       |    2 
 cscope.out                         |314340 +++++++++++++++++++++++++++++++++++++
 jffs2reader.c                      |    1 
 mkfs.jffs2.c                       |   49 
 mkfs.ubifs/compr.c                 |    1 
 tests/fs-tests/lib/tests.o         |binary
 tests/ubi-tests/.common.c.dep      |   38 
 tests/ubi-tests/.integ.c.dep       |   38 
 tests/ubi-tests/.io_basic.c.dep    |   33 
 tests/ubi-tests/.io_paral.c.dep    |   32 
 tests/ubi-tests/.io_read.c.dep     |   33 
 tests/ubi-tests/.io_update.c.dep   |   33 
 tests/ubi-tests/.mkvol_bad.c.dep   |   24 
 tests/ubi-tests/.mkvol_basic.c.dep |   24 
 tests/ubi-tests/.mkvol_paral.c.dep |   27 
 tests/ubi-tests/.rsvol.c.dep       |   33 
 tests/ubi-tests/.volrefcnt.c.dep   |   31 
 tests/ubi-tests/common.o           |binary
 tests/ubi-tests/integ              |binary
 tests/ubi-tests/io_basic           |binary
 tests/ubi-tests/io_paral           |binary
 tests/ubi-tests/io_read            |binary
 tests/ubi-tests/io_update          |binary
 tests/ubi-tests/libubi.a           |binary
 tests/ubi-tests/libubi.o           |binary
 tests/ubi-tests/mkvol_bad          |binary
 tests/ubi-tests/mkvol_basic        |binary
 tests/ubi-tests/mkvol_paral        |binary
 tests/ubi-tests/rsvol              |binary
 tests/ubi-tests/volrefcnt          |binary
 ubi-utils/cscope.out               |164861 +++++++++++++++++++
 ubi-utils/libmtd.a                 |binary
 32 files changed, 479573 insertions(+), 27 deletions(-)

Care to fix that?

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2010-10-18 20:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-14 21:54 Latest mkfs.jffs2 is broken H Hartley Sweeten
2010-10-15  6:14 ` Artem Bityutskiy
2010-10-15  8:35   ` Peter Korsgaard
2010-10-15  8:43     ` Artem Bityutskiy
2010-10-15  8:52       ` Peter Korsgaard
2010-10-16 15:49         ` Artem Bityutskiy
2010-10-16 20:19           ` Peter Korsgaard
2010-10-18 20:51           ` Peter Korsgaard [this message]
2010-10-19  4:49             ` Artem Bityutskiy
2010-10-19  8:38               ` Peter Korsgaard

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=871v7n442j.fsf@macbook.be.48ers.dk \
    --to=jacmet@sunsite.dk \
    --cc=dedekind1@gmail.com \
    --cc=hartleys@visionengravers.com \
    --cc=linux-mtd@lists.infradead.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.