From: David Masover <ninja@slaphack.com>
To: Reiserfs List <reiserfs-list@namesys.com>
Subject: backporting?
Date: Tue, 18 Jul 2006 16:03:15 -0500 [thread overview]
Message-ID: <44BD4C93.504@slaphack.com> (raw)
I also wanted to say that I'm back -- all problems with my mailserver
bouncing messages should be fixed now.
But I do have a legitimate question: I get my Reiser4 as the
reiser4-for-2.6 patches. Do new versions ever get backported to older
kernel versions?
This is not a feature request -- if there's no backport, I'll do
without. I'm currently stuck on 2.6.13.4 because of a network driver,
but it's probably easier to fix a network driver than to backport a
filesystem.
next reply other threads:[~2006-07-18 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 21:03 David Masover [this message]
2006-07-19 7:19 ` backporting? Vladimir V. Saveliev
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=44BD4C93.504@slaphack.com \
--to=ninja@slaphack.com \
--cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.