public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Chubb <peter@chubb.wattle.id.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] A start at large file and filesystem support
Date: Wed, 24 Apr 2002 10:26:21 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905509@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905504@msgid-missing>

>>>>> "David" = David Mosberger <davidm@napali.hpl.hp.com> writes:

David> Good work!  Since this really doesn't touch any ia64 files:
David> will you work directly with the respective maintainers to get
David> this into the official 2.5 tree?

Sure.  I'll need to split off the changes from the IA64 changes, and
the patch currently will crash on systems that don't use 64-bit
addressing (because of the way the page cache works).  I'd like to get
some people who have enormous filesystems and 64-bit machines to give
the patch a go.

Peter> If you're bitkeeper-enabled, you can pull the patch from
Peter> bk://gelato.unsw.edu.au:2022

David> Not sure how others feel about this, but I for one still like
David> to get diff -u-style patches.  It's just so much faster to get
David> a quick idea of what the patch does.

That's why I provided both -- but 1.8M of diffs is a bit much for an
email.  (I had to change the definition of a couple of interface
functions, which meant lots of files have two line changes)

Peter C


  parent reply	other threads:[~2002-04-24 10:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-24  5:25 [Linux-ia64] A start at large file and filesystem support peterc
2002-04-24  6:12 ` David Mosberger
2002-04-24 10:26 ` Peter Chubb [this message]
2002-04-25 18:40 ` David Mosberger
2002-04-25 22:39 ` Peter Chubb

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=marc-linux-ia64-105590701905509@msgid-missing \
    --to=peter@chubb.wattle.id.au \
    --cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox