From: Wolfram Sang <wsa@the-dreams.de>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: linux-mm@kvack.org, Dan Streetman <ddstreet@ieee.org>,
Seth Jennings <sjenning@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: Using best practices for big software change possibilities
Date: Sun, 21 May 2017 12:27:51 +0200 [thread overview]
Message-ID: <20170521102750.ljgvdw2btuks3tqf@ninjato> (raw)
In-Reply-To: <82cfcf3e-0089-0629-f10c-e01346487f6a@users.sourceforge.net>
[-- Attachment #1: Type: text/plain, Size: 300 bytes --]
> How do you think about to resolve them by additional means besides mail exchange?
That can work. E.g. meeting at conferences often solved mail
communication problems.
For now, I still wonder why you were unsure about grouping the changes
into one patch? Maybe there is something to be learned?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: linux-mm@kvack.org, Dan Streetman <ddstreet@ieee.org>,
Seth Jennings <sjenning@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: Using best practices for big software change possibilities
Date: Sun, 21 May 2017 10:27:51 +0000 [thread overview]
Message-ID: <20170521102750.ljgvdw2btuks3tqf@ninjato> (raw)
In-Reply-To: <82cfcf3e-0089-0629-f10c-e01346487f6a@users.sourceforge.net>
[-- Attachment #1: Type: text/plain, Size: 300 bytes --]
> How do you think about to resolve them by additional means besides mail exchange?
That can work. E.g. meeting at conferences often solved mail
communication problems.
For now, I still wonder why you were unsure about grouping the changes
into one patch? Maybe there is something to be learned?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-05-21 10:27 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-21 8:23 [PATCH 0/3] zswap: Adjustments for three function implementations SF Markus Elfring
2017-05-21 8:23 ` SF Markus Elfring
2017-05-21 8:23 ` SF Markus Elfring
2017-05-21 8:25 ` [PATCH 1/3] zswap: Delete an error message for a failed memory allocation in zswap_pool_create() SF Markus Elfring
2017-05-21 8:25 ` SF Markus Elfring
2017-05-21 8:25 ` SF Markus Elfring
2017-05-30 23:18 ` Dan Streetman
2017-05-30 23:18 ` Dan Streetman
2017-05-30 23:18 ` Dan Streetman
2017-05-21 8:26 ` [PATCH 2/3] zswap: Improve a size determination in zswap_frontswap_init() SF Markus Elfring
2017-05-21 8:26 ` SF Markus Elfring
2017-05-21 8:26 ` SF Markus Elfring
2017-05-30 23:19 ` Dan Streetman
2017-05-30 23:19 ` Dan Streetman
2017-05-30 23:19 ` Dan Streetman
2017-05-21 8:27 ` [PATCH 3/3] zswap: Delete an error message for a failed memory allocation in zswap_dstmem_prepare() SF Markus Elfring
2017-05-21 8:27 ` SF Markus Elfring
2017-05-21 8:27 ` SF Markus Elfring
2017-05-21 8:47 ` Wolfram Sang
2017-05-21 8:47 ` [PATCH 3/3] zswap: Delete an error message for a failed memory allocation in zswap_dstmem_prepar Wolfram Sang
2017-05-21 9:40 ` zswap: Delete an error message for a failed memory allocation in zswap_dstmem_prepare() SF Markus Elfring
2017-05-21 9:40 ` SF Markus Elfring
2017-05-21 9:40 ` SF Markus Elfring
2017-05-21 9:56 ` Wolfram Sang
2017-05-21 9:56 ` Wolfram Sang
2017-05-21 10:12 ` Using best practices for big software change possibilities SF Markus Elfring
2017-05-21 10:12 ` SF Markus Elfring
2017-05-21 10:12 ` SF Markus Elfring
2017-05-21 10:27 ` Wolfram Sang [this message]
2017-05-21 10:27 ` Wolfram Sang
2017-05-21 10:45 ` SF Markus Elfring
2017-05-21 10:45 ` SF Markus Elfring
2017-05-21 10:45 ` SF Markus Elfring
2017-05-30 23:20 ` [PATCH 3/3] zswap: Delete an error message for a failed memory allocation in zswap_dstmem_prepare() Dan Streetman
2017-05-30 23:20 ` Dan Streetman
2017-05-30 23:20 ` [PATCH 3/3] zswap: Delete an error message for a failed memory allocation in zswap_dstmem_prepar Dan Streetman
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=20170521102750.ljgvdw2btuks3tqf@ninjato \
--to=wsa@the-dreams.de \
--cc=ddstreet@ieee.org \
--cc=elfring@users.sourceforge.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sjenning@redhat.com \
/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.