From: Ivan Shapovalov <intelfx@intelfx.name>
To: Edward Shishkin <edward.shishkin@gmail.com>,
Reiserfs development mailing list
<reiserfs-devel@vger.kernel.org>
Subject: Re: [PATCH] reiser4: port for Linux-4.5
Date: Wed, 06 Apr 2016 18:37:20 +0300 [thread overview]
Message-ID: <1459957040.5177.3.camel@intelfx.name> (raw)
In-Reply-To: <57052A06.2020207@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
On 2016-04-06 at 17:23 +0200, Edward Shishkin wrote:
> On 04/06/2016 03:22 AM, Ivan Shapovalov wrote:
> >
> > [...]
> > By the way: I've noticed many times that the resulting squashed
> > patch
> > which you put on sourceforge is _different_ from what can be
> > composed
> > using incremental patches you send on the ML.
>
> I never announced any peculiar properties of the patches that I
> send to the mailing list. This is mostly for me (to look at the mail
> archive and to refresh memory.
OK. Life could've been easier...
> > Maybe you could finally consider having a git repo somewhere (e. g.
> > on
> > github)? It would be much easier to work with the code (and, for me
> > in
> > particular, to learn how it works) this way.
>
> I'll consider it sooner or later, since all Namesys archives are
> git-based, but it seems that probably "later", because currently I am
> very busy..
ditto.
Thanks anyway,
--
Ivan Shapovalov / intelfx /
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-04-06 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 9:20 [PATCH] reiser4: port for Linux-4.5 Edward Shishkin
2016-04-06 0:42 ` Ivan Shapovalov
2016-04-06 15:21 ` Edward Shishkin
2016-04-06 15:26 ` Ivan Shapovalov
2016-04-06 1:22 ` Ivan Shapovalov
2016-04-06 15:23 ` Edward Shishkin
2016-04-06 15:37 ` Ivan Shapovalov [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=1459957040.5177.3.camel@intelfx.name \
--to=intelfx@intelfx.name \
--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).