reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivan Shapovalov <intelfx100@gmail.com>
To: doiggl@velocitynet.com.au
Cc: reiserfs-devel@vger.kernel.org,
	Edward Shishkin <edward.shishkin@gmail.com>
Subject: Re: In the future, will a r4 patch be created for linux 3.18.x series and patches
Date: Thu, 29 Jan 2015 02:21:54 +0300	[thread overview]
Message-ID: <1422487314.8468.4.camel@gmail.com> (raw)
In-Reply-To: <d72614d46b84a7c4a1f1728e4742232b@mail.velocitynet.com.au>

[-- Attachment #1: Type: text/plain, Size: 678 bytes --]

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?

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).

-- 
Ivan Shapovalov / intelfx /

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 213 bytes --]

  reply	other threads:[~2015-01-28 23:21 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 [this message]
2015-01-29 19:31   ` 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=1422487314.8468.4.camel@gmail.com \
    --to=intelfx100@gmail.com \
    --cc=doiggl@velocitynet.com.au \
    --cc=edward.shishkin@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).