From: Larry McVoy <lm@bitmover.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-2.5.4-pre1 - bitkeeper testing
Date: Wed, 6 Feb 2002 15:06:02 -0800 [thread overview]
Message-ID: <20020206150602.W7674@work.bitmover.com> (raw)
In-Reply-To: <Pine.LNX.4.31.0202051928330.2375-100000@cesium.transmeta.com> <20020206193818.GA158@elf.ucw.cz>
In-Reply-To: <20020206193818.GA158@elf.ucw.cz>; from pavel@suse.cz on Wed, Feb 06, 2002 at 08:38:18PM +0100
On Wed, Feb 06, 2002 at 08:38:18PM +0100, Pavel Machek wrote:
> Hey, this looks very good! At this level of verbosity, it might be
> nice to also list modified files, but this is really good.
He generated that listing with "bk changes", you want "bk changes -v", which
I included below, but doesn't have any more useful info (yet) because the
comments are all auto generated from the email.
We will stick up a web page someplace that says "send Linus comments
like this if you want individual file comments to be different", and is
totally BK agnostic, i.e., you can send them with a regular diff -Nur
style patch and the import tools will do the right thing. Then the
verbose listing will start to be useful.
--lm
ChangeSet
1.237 02/02/06 10:57:18 reiser@namesys.com +1 -0
[PATCH] reiserfs fix for inodes with wrong item versions (2.5)
This is hopefully last bugfix for a bug introduced by struct inode splittin
g.
Because of setting i_flags to some value and then cleaning the i_flags
contents later, on-disk items received wrong item version ob v3.6 filesyste
ms
fs/reiserfs/inode.c
1.34 02/02/06 10:57:17 reiser@namesys.com +7 -7
reiserfs fix for inodes with wrong item versions (2.5)
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2002-02-06 23:06 UTC|newest]
Thread overview: 104+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 3:37 linux-2.5.4-pre1 - bitkeeper testing Linus Torvalds
2002-02-06 6:50 ` Andreas Dilger
2002-02-06 7:50 ` Reid Hekman
2002-02-06 8:03 ` Larry McVoy
2002-02-06 19:35 ` Christoph Hellwig
2002-02-06 19:45 ` Tom Rini
2002-02-06 20:44 ` Wayne Scott
2002-02-06 20:35 ` Larry McVoy
2002-02-06 22:25 ` Mike Fedyk
2002-02-06 15:17 ` Florian Weimer
2002-02-06 15:32 ` Rik van Riel
2002-02-06 16:54 ` Larry McVoy
2002-02-06 22:19 ` Rob Landley
2002-02-06 17:30 ` Roman Zippel
2002-02-06 17:33 ` Linus Torvalds
2002-02-06 19:58 ` Roman Zippel
2002-02-06 23:36 ` Linus Torvalds
2002-02-06 23:54 ` Larry McVoy
2002-02-07 8:07 ` Stelian Pop
2002-02-07 16:36 ` Linus Torvalds
2002-02-07 17:26 ` Larry McVoy
2002-02-07 19:46 ` Stelian Pop
2002-02-08 0:29 ` Andreas Dilger
2002-02-08 5:28 ` Troy Benjegerdes
2002-02-08 6:06 ` Larry McVoy
2002-02-08 6:14 ` Troy Benjegerdes
2002-02-08 6:49 ` Andreas Dilger
2002-02-07 10:50 ` Roman Zippel
2002-02-06 19:38 ` Pavel Machek
2002-02-06 23:06 ` Larry McVoy [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-06 7:33 Jeramy B. Smith
2002-02-06 15:15 ` Florian Weimer
2002-02-07 16:50 ` Jan Harkes
2002-02-07 23:06 ` Tom Lord
2002-02-07 21:23 ` Daniel Phillips
2002-02-08 1:02 ` Tom Lord
2002-02-07 21:23 ` Paul P Komkoff Jr
2002-02-07 21:28 ` Larry McVoy
2002-02-07 21:25 ` Larry McVoy
2002-02-08 2:32 ` Tom Lord
2002-02-08 15:33 ` Pavel Machek
2002-02-08 21:35 ` Larry McVoy
2002-02-11 8:20 ` Josh MacDonald
2002-02-11 15:00 ` Larry McVoy
2002-02-11 20:25 ` Pavel Machek
2002-02-11 22:14 ` Larry McVoy
2002-02-12 5:17 ` Tom Lord
2002-02-12 3:59 ` Theodore Tso
2002-02-12 6:19 ` Bernd Eckenfels
2002-02-12 20:28 ` Tom Lord
2002-02-12 22:54 ` Larry McVoy
2002-02-13 0:52 ` Daniel Phillips
2002-02-13 9:41 ` Tom Lord
2002-02-13 10:35 ` Roman Zippel
2002-02-12 11:01 ` Josh MacDonald
2002-02-12 11:15 ` Jeff Garzik
2002-02-18 18:10 ` Eric W. Biederman
2002-03-10 8:36 ` Hans Reiser
2002-03-10 19:41 ` Itai Nahshon
2002-03-10 20:19 ` Hans Reiser
2002-03-10 21:16 ` Rob Turk
2002-03-10 21:34 ` Alan Cox
2002-03-10 21:23 ` Rik van Riel
2002-03-11 8:22 ` Hans Reiser
2002-03-10 21:28 ` Alexander Viro
2002-03-11 11:04 ` Mark H. Wood
2002-03-11 9:46 ` Harald Arnesen
2002-03-10 21:37 ` Richard Gooch
2002-03-11 5:48 ` Hans Reiser
2002-03-11 5:52 ` Alexander Viro
2002-03-11 6:15 ` Hans Reiser
2002-03-11 6:37 ` Alexander Viro
2002-03-11 6:42 ` Richard Gooch
2002-03-11 13:13 ` yodaiken
2002-03-11 15:51 ` Hans Reiser
2002-03-11 16:08 ` yodaiken
2002-03-11 16:56 ` Hans Reiser
2002-03-11 22:51 ` James Antill
2002-03-12 7:58 ` Hans Reiser
2002-03-12 22:37 ` Andrew Pimlott
2002-03-13 8:09 ` Hans Reiser
2002-03-13 15:10 ` Andrew Pimlott
2002-03-13 9:39 ` Geert Uytterhoeven
2002-03-13 14:37 ` Andrew Pimlott
2002-03-13 16:26 ` Larry McVoy
2002-03-13 16:30 ` Andrew Pimlott
2002-03-13 19:18 ` Hans Reiser
2002-03-11 14:05 ` Luigi Genoni
2002-03-11 10:46 ` Mark H. Wood
2002-03-11 11:32 ` Hans Reiser
2002-03-11 15:29 ` Steven Cole
2002-03-11 16:08 ` Hans Reiser
2002-03-11 16:25 ` Steven Cole
2002-03-11 17:08 ` Hans Reiser
2002-03-11 17:16 ` Nikita Danilov
2002-03-11 18:41 ` Steven Cole
2002-03-11 19:15 ` Hans Reiser
2002-03-11 21:33 ` Steven Cole
2002-03-11 21:54 ` Richard B. Johnson
2002-03-11 22:01 ` Richard B. Johnson
2002-03-11 22:19 ` Steven Cole
2002-03-12 0:14 ` Robert Pfister
2002-03-12 1:28 ` Mark H. Wood
2002-03-12 18:08 Thunder from the hill
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=20020206150602.W7674@work.bitmover.com \
--to=lm@bitmover.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=torvalds@transmeta.com \
/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