From: Larry McVoy <lm@bitmover.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Andrew Morton <akpm@digeo.com>,
lm@bitmover.com, linux-kernel@vger.kernel.org
Subject: Re: 2.5 changeset 1.952.4.2 corrupt in fs/jfs/inode.c
Date: Wed, 5 Feb 2003 15:29:22 -0800 [thread overview]
Message-ID: <20030205232922.GA14131@work.bitmover.com> (raw)
In-Reply-To: <20030205195151.GJ19678@dualathlon.random>
> it might be simply an error in the tarball, maybe Linus's tree isn't in
> full sync with bk head. But something definitely is corrupt between
> tarball and bk.
That is an incorrect statement. You are comparing a moving target with
a snapshot. If you roll the moving target back to the snapshot point
you get the tarball contents.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-02-05 23:19 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 17:40 2.5 changeset 1.952.4.2 corrupt in fs/jfs/inode.c Andrea Arcangeli
2003-02-05 18:23 ` Andrew Morton
2003-02-05 18:45 ` Andrea Arcangeli
2003-02-05 19:42 ` Dave Jones
2003-02-05 20:06 ` Andrea Arcangeli
2003-02-05 19:43 ` Andrew Morton
2003-02-05 19:51 ` Andrea Arcangeli
2003-02-05 20:09 ` Andrew Morton
2003-02-05 20:18 ` Andrea Arcangeli
2003-02-05 20:33 ` Andrew Morton
2003-02-05 23:29 ` Larry McVoy [this message]
2003-02-05 20:11 ` Matt Reppert
2003-02-05 20:24 ` Andrea Arcangeli
2003-02-05 20:56 ` Linus Torvalds
2003-02-05 20:25 ` Linus Torvalds
2003-02-05 23:31 ` Larry McVoy
2003-02-05 23:37 ` Christoph Hellwig
2003-02-05 23:57 ` Larry McVoy
2003-02-06 0:22 ` Robert Love
2003-02-06 16:58 ` Andreas Dilger
2003-02-06 17:30 ` Larry McVoy
2003-02-06 17:55 ` Matt Reppert
2003-02-07 16:18 ` glibc-2.3 [Was: Re: 2.5 changeset 1.952.4.2 corrupt in fs/jfs/inode.c] Horst von Brand
2003-02-07 18:06 ` Larry McVoy
2003-02-06 0:37 ` 2.5 changeset 1.952.4.2 corrupt in fs/jfs/inode.c Chris Funderburg (at home)
2003-02-06 0:45 ` Alan Cox
2003-02-05 23:51 ` Larry McVoy
2003-02-06 0:02 ` Mitch Adair
2003-02-06 0:08 ` Larry McVoy
2003-02-06 10:02 ` Nick Craig-Wood
2003-02-09 18:37 ` Kenneth Johansson
2003-02-05 19:46 ` Sam Ravnborg
2003-02-05 20:04 ` Dave Kleikamp
2003-02-05 20:10 ` Andrea Arcangeli
2003-02-05 20:16 ` Dave Kleikamp
2003-02-05 20:34 ` Sam Ravnborg
2003-02-05 20:51 ` Andrea Arcangeli
2003-02-05 22:09 ` Linus Torvalds
2003-02-06 10:46 ` Roman Zippel
2003-02-06 11:09 ` Andreas Schwab
2003-02-05 21:56 ` Linus Torvalds
2003-02-07 14:56 ` Pavel Machek
2003-02-08 18:28 ` Larry McVoy
2003-02-08 19:36 ` Martin J. Bligh
2003-02-09 10:57 ` Pavel Machek
2003-02-09 14:15 ` Andrea Arcangeli
2003-02-13 1:50 ` Jamie Lokier
2003-02-13 1:57 ` Jamie Lokier
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=20030205232922.GA14131@work.bitmover.com \
--to=lm@bitmover.com \
--cc=akpm@digeo.com \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.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.