public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Dave Kleikamp <shaggy@austin.ibm.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 21:34:45 +0100	[thread overview]
Message-ID: <20030205203445.GA4467@mars.ravnborg.org> (raw)
In-Reply-To: <20030205201055.GL19678@dualathlon.random>

On Wed, Feb 05, 2003 at 09:10:55PM +0100, Andrea Arcangeli wrote:
> > Andrea,
> > 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?

cset 1.952.1.4 is the one that Linus released 2.5.59 on.
Now I started doing some development based on cset 1.875 - a few days older.

Tomorrow Linus release a new kernel, cset 1.973 for example.
Next week Linus merge my work, that will be numbered 1.875.1.1..1.875.1.3

You will see that my cset will be listed on the web on the date where
I did the commit, but it will not appear on kernel.org until
Linus merge my stuff.
So you cannot deduct from the numbers in what release a certain cset belongs.

The fact that cset's appear on the web as they are orginally committed
is annoying tracking the kernel, and Larry sometime ago noted that they
may do some changes in that respect.

	Sam

  parent reply	other threads:[~2003-02-05 20:25 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
2003-02-05 20:34     ` Sam Ravnborg [this message]
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=20030205203445.GA4467@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=shaggy@austin.ibm.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