All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Shapovalov <intelfx100@gmail.com>
To: Edward Shishkin <edward.shishkin@gmail.com>,
	Reiserfs development mailing list
	<reiserfs-devel@vger.kernel.org>
Subject: Re: Reiser4 for Linux-4.1
Date: Fri, 04 Sep 2015 03:25:03 +0300	[thread overview]
Message-ID: <1441326303.12422.11.camel@gmail.com> (raw)
In-Reply-To: <1441325851.12422.5.camel@gmail.com>

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

On 2015-09-04 at 03:17 +0300, Ivan Shapovalov wrote:
> On 2015-08-07 at 14:02 +0200, Edward Shishkin wrote:
> > Changes since Reiser4 for Linux-4.0.4:
> > 
> > Fixed a problem appearing when running under "no space left on
> > device". It also could be the reason of sporadic silent non
> > -reproducible
> > data corruptions, that were reported periodically.
> > 
> > The fixup was backported to Linux-4.0 (see reiser4-for-4.0.9).
> > If you need a backport for older kernel, then let me know.
> > 
> > Please, find at
> > http://sourceforge.net/projects/reiser4/files/reiser4-for-linux-4.x
> > /
> 
> Hi Edward,
> 
> could you please send the fixup in a separate patch/mail (git
> -format)?

While at it, could you please consider having a dedicated git tree for
reiser4, which would serve same purposes as the sourceforge project,
but with per-commit granularity instead of per-release?

I'm trying to maintain one (by simply picking all patches that fly over
the mailing list), but, to my surprise, it seems to have slightly
diverged from your releases.

-- 
Ivan Shapovalov / intelfx /


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

  reply	other threads:[~2015-09-04  0:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07 12:02 Reiser4 for Linux-4.1 Edward Shishkin
2015-09-04  0:17 ` Ivan Shapovalov
2015-09-04  0:25   ` Ivan Shapovalov [this message]
2015-09-04  7:18   ` Edward Shishkin
2015-09-04  7:23     ` 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=1441326303.12422.11.camel@gmail.com \
    --to=intelfx100@gmail.com \
    --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 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.