From: Joe Perches <joe@perches.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-next@vger.kernel.org, sfr@canb.auug.org.au, mhocko@suse.cz
Subject: Re: mmotm 2014-10-29-14-19 uploaded
Date: Wed, 29 Oct 2014 14:59:36 -0700 [thread overview]
Message-ID: <1414619976.2542.1.camel@perches.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1410292233340.5308@nanos>
On Wed, 2014-10-29 at 22:37 +0100, Thomas Gleixner wrote:
> On Wed, 29 Oct 2014, akpm@linux-foundation.org wrote:
> > This mmotm tree contains the following patches against 3.18-rc2:
> > (patches marked "*" will be included in linux-next)
> >
> > * kernel-posix-timersc-code-clean-up.patch
>
> Can you please drop this pointless churn? We really can replace all
> that stuff with a shell script and let it run over the tree every now
> and then.
Should any automated code reformatting really be done
by an unsupervised or unreviewed shell script?
Likely not.
--
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:[~2014-10-29 21:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 21:20 akpm
2014-10-29 21:37 ` Thomas Gleixner
2014-10-29 21:59 ` Joe Perches [this message]
2014-10-30 9:02 ` Richard Weinberger
2014-10-30 8:47 ` [PATCH] mm-cma-make-kmemleak-ignore-cma-regions-fix Michal Hocko
2014-10-30 8:56 ` Michal Hocko
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=1414619976.2542.1.camel@perches.com \
--to=joe@perches.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.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