From: Edward Shishkin <edward.shishkin@gmail.com>
To: Ivan Shapovalov <intelfx100@gmail.com>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: A best approach to get a summary of r4-conflicting kernel changes from 2.6.39
Date: Thu, 23 Aug 2012 19:39:12 +0200 [thread overview]
Message-ID: <50366AC0.8000903@gmail.com> (raw)
In-Reply-To: <5669697.fA5P36S773@intelfx-laptop>
Hi Ivan,
Such summaries can be found at http://kernelnewbies.org/RecentChanges
(see section "VFS" of each summary).
Reiser4 makes a friendship with Linux VFS in all items except
fs-writeback. So I think it will be enough just to look at respective
changes, say, in ReiserFS (v3).
As to modifications in fs-writeback: Reiser4 has been adjusted to
3.1 stuff by Marcin Baczyński (I can forward the patch). I believe
this can be easily ported also to the next kernels.
Thanks,
Edward.
P.S.
Here I explained bits where reiser4 clashes with fs-writeback:
http://marc.info/?l=reiserfs-devel&m=132603099732236&w=2
On 08/17/2012 10:53 PM, Ivan Shapovalov wrote:
> Hello,
>
> What is the best way to get some "summary" of changes that the kernel had
> undergone from 2.6.39 (last reiser4-compatible) to current? I need not all
> changes, but only those which make the current kernel reiser4-incompatible.
> In particular, will "git log" suffice - and if yes, to which files/directories
> shall it be applied?
>
> Thanks in advance,
> Ivan Shapovalov
> --
> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-08-23 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 20:53 A best approach to get a summary of r4-conflicting kernel changes from 2.6.39 Ivan Shapovalov
2012-08-23 17:39 ` Edward Shishkin [this message]
2012-08-26 16:21 ` dimas
[not found] ` <504769CD.8070302@gmail.com>
[not found] ` <504BD545.3020908@gmail.com>
[not found] ` <29939407.LWCMkzCiDx@intelfx-laptop>
2012-09-10 22:07 ` Edward Shishkin
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=50366AC0.8000903@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=intelfx100@gmail.com \
--cc=reiserfs-devel@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 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.