From: Anders Gustafsson <andersg@0x63.nu>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: torvalds@transmeta.com
Subject: Re: [XFS] add missing file xfs_iomap.c
Date: Mon, 16 Dec 2002 03:34:53 +0100 [thread overview]
Message-ID: <20021216023453.GA19659@gagarin> (raw)
In-Reply-To: <200212160004.gBG04g130091@hera.kernel.org>
On Sun, Dec 15, 2002 at 10:07:43PM +0000, Linux Kernel Mailing List wrote:
> # This patch includes the following deltas:
> # ChangeSet 1.940.1.1 -> 1.940.1.2
> # (new) -> 1.1 fs/xfs/xfs.ko
> #
>
> xfs.ko |binary
> 1 files changed
>
>
> Binary files a/fs/xfs/xfs.ko and b/fs/xfs/xfs.ko differ
A .ko in the bitkeeper?
This can't be correct?
--
Anders Gustafsson - andersg@0x63.nu - http://0x63.nu/
next parent reply other threads:[~2002-12-16 2:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200212160004.gBG04g130091@hera.kernel.org>
2002-12-16 2:34 ` Anders Gustafsson [this message]
2002-12-16 3:58 ` /proc/cpuinfo and hyperthreading Scott Robert Ladd
2002-12-16 4:02 ` Robert Love
2002-12-16 4:13 ` Scott Robert Ladd
2002-12-16 6:28 ` Zwane Mwaikambo
2002-12-16 6:35 ` Zwane Mwaikambo
2002-12-16 13:38 ` Scott Robert Ladd
2002-12-16 13:54 ` Brian Jackson
2002-12-16 14:10 ` Richard B. Johnson
2002-12-16 14:56 ` Scott Robert Ladd
2002-12-16 15:11 ` Måns Rullgård
2002-12-16 15:44 ` HT Benchmarks (was: /proc/cpuinfo and hyperthreading) Scott Robert Ladd
2002-12-16 22:38 ` J.A. Magallon
2002-12-16 23:21 ` Scott Robert Ladd
2002-12-16 23:27 ` J.A. Magallon
2002-12-17 11:03 ` Denis Vlasenko
2002-12-17 20:44 ` H. Peter Anvin
2002-12-16 23:50 ` H. Peter Anvin
2002-12-17 19:27 ` Bill Davidsen
2002-12-16 15:52 ` /proc/cpuinfo and hyperthreading Andrew Theurer
2002-12-16 14:08 ` Dave Jones
2002-12-16 14:36 ` Scott Robert Ladd
2002-12-16 4:39 ` [XFS] add missing file xfs_iomap.c Linus Torvalds
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=20021216023453.GA19659@gagarin \
--to=andersg@0x63.nu \
--cc=linux-kernel@vger.kernel.org \
--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