From: Blaisorblade <blaisorblade@yahoo.it>
To: Antoine Martin <antoine@nagafix.co.uk>
Cc: UML devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: [uml-devel] Re: hppfs
Date: Mon, 19 Dec 2005 20:25:34 +0100 [thread overview]
Message-ID: <200512192025.50354.blaisorblade@yahoo.it> (raw)
In-Reply-To: <1134932635.10491.77.camel@localhost.localdomain>
[-- Attachment #1.1: Type: text/plain, Size: 1215 bytes --]
On Sunday 18 December 2005 20:03, Antoine Martin wrote:
> Paolo,
> What is the state of hppfs? You sent 12 patches in September, and there
> was some discussion with Al Viro about some of the patches (but no new
> patches) Can I try to apply them to 2.6.14?
> Thanks
> Antoine
Thanks to you.
I have an updated version of those patches - incorporated Viro suggestions and
some of the other fixes he requested (not everything). I've exported
everything and attached the thing.
When you test that, a short 3-liners "test it this way" is appreciated.
Ah, while at it, if you can find a file bigger than 4k to test?
The existing code to handle that was poorlessly broken and had no chance of
working, patches fix that.
Btw, can you use quilt? Not that
while read i; do
patch -p1 < patches/$i
done < patches/series
isn't supposed to work (totally untested), together with "man tac" for
unapplying.
But quilt is more powerful and easier to use. Not that I care myself.
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
[-- Attachment #1.2: hppfs-patches.tar.bz2 --]
[-- Type: application/x-tbz, Size: 11401 bytes --]
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-12-19 19:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-18 19:03 [uml-devel] hpps Antoine Martin
2005-12-19 19:25 ` Blaisorblade [this message]
2005-12-19 19:28 ` [uml-devel] hpps Blaisorblade
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=200512192025.50354.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=antoine@nagafix.co.uk \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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