From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Wolfram Sang <wsa@the-dreams.de>
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:12:39 +0200 [thread overview]
Message-ID: <82cfcf3e-0089-0629-f10c-e01346487f6a@users.sourceforge.net> (raw)
In-Reply-To: <20170521095654.bzpaa2obfszrajgb@ninjato>
> Have you read my LWN article "Best practices for a big patch series"?
>
> https://lwn.net/Articles/585782/
Yes.
>> This can also happen as a side effect if such a source code search pattern
>> will point hundreds of places out for further software development considerations.
>> How would you prefer to clarify the remaining update candidates there?
>
> Maybe the article mentioned can provice further guidance?
Partly, yes.
I am trying to achieve some software improvements also for special change patterns.
This approach can trigger corresponding communication difficulties.
How do you think about to resolve them by additional means besides mail exchange?
Regards,
Markus
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-05-21 10:12 UTC|newest]
Thread overview: 13+ 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:25 ` [PATCH 1/3] zswap: Delete an error message for a failed memory allocation in zswap_pool_create() SF Markus Elfring
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-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:47 ` Wolfram Sang
2017-05-21 9:40 ` SF Markus Elfring
2017-05-21 9:56 ` Wolfram Sang
2017-05-21 10:12 ` SF Markus Elfring [this message]
2017-05-21 10:27 ` Using best practices for big software change possibilities Wolfram Sang
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
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=82cfcf3e-0089-0629-f10c-e01346487f6a@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=ddstreet@ieee.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sjenning@redhat.com \
--cc=wsa@the-dreams.de \
/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).