From: Dave Kleikamp <shaggy@austin.ibm.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: 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 14:16:01 -0600 [thread overview]
Message-ID: <200302051416.01543.shaggy@austin.ibm.com> (raw)
In-Reply-To: <20030205201055.GL19678@dualathlon.random>
On Wednesday 05 February 2003 14:10, Andrea Arcangeli wrote:
> On Wed, Feb 05, 2003 at 02:04:21PM -0600, Dave Kleikamp wrote:
> > The change from block_truncate_page to nobh_truncate_page was done
> > in Changeset 1.879.43.1. This was created on January 9th, but not
> > merged into Linus' tree until Monday, so it is not in 2.5.59. I
> > think the
>
> if you think it's normal the thing sounds very messy. I mean, how can
> a changeset be numbered 1.879.43.1 and not be included in 2.5.59?
>
> The way I understood it is that when Linus merges "stuff", this
> "stuff" gets a changeset number in the future, not in the past. No
> matter if the "stuff" was created in the past. Is this the case or
> not?
I don't understand the changeset numbering myself, so I guess Larry will
have to answer this one.
> I mean, somehow there must be a way to number the changesets so that
> applying them in order generates something coherent.
>
> Andrea
--
David Kleikamp
IBM Linux Technology Center
next prev parent reply other threads:[~2003-02-05 20:06 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
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 [this message]
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=200302051416.01543.shaggy@austin.ibm.com \
--to=shaggy@austin.ibm.com \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.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;
as well as URLs for NNTP newsgroup(s).