From: Edward Shishkin <edward.shishkin@gmail.com>
To: Ivan Shapovalov <intelfx100@gmail.com>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: In the future, will a r4 patch be created for linux 3.18.x series and patches
Date: Thu, 29 Jan 2015 20:31:53 +0100 [thread overview]
Message-ID: <54CA8AA9.607@gmail.com> (raw)
In-Reply-To: <1422487314.8468.4.camel@gmail.com>
On 01/29/2015 12:21 AM, Ivan Shapovalov wrote:
> On 2015-01-14 at 20:18 +1100, doiggl@velocitynet.com.au wrote:
>> Hello,
>> In the future, will a r4 patch be created for linux 3.18.x series and
>> patches
>>
>> Just asking.
>> Cheers Glenn
> Actually, reiser4 does not need porting for 3.17 -> 3.18, there's just
> a single merge conflict. I've been running 3.18 with reiser4 this way
> all time since its release...
>
> to Edward: maybe you could release reiser4-for-3.18 just with that merge
> conflict fixed?
Ok.
> P. S.: I haven't yet tested your precise discard implementation. I've
> been pretty busy with the exam session (which has just ended, so I'll
> get to testing it in short time).
>
Congrats!
The first session in MIPT is really a survival test.
At least it was so in 198X..
Edward.
prev parent reply other threads:[~2015-01-29 19:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 9:18 In the future, will a r4 patch be created for linux 3.18.x series and patches doiggl
2015-01-28 23:21 ` Ivan Shapovalov
2015-01-29 19:31 ` Edward Shishkin [this message]
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=54CA8AA9.607@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).