From: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Linus Torvalds
<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Cc: Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [GIT PULL] cgroup fixes for v3.17-rc4
Date: Mon, 8 Sep 2014 13:50:54 +0900 [thread overview]
Message-ID: <20140908045054.GA8526@mtj.dyndns.org> (raw)
In-Reply-To: <CA+55aFw+L1EUDEmAATDtGj_ngHos842jHLddAszboRy4b0pn2A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hello, Linus.
On Sun, Sep 07, 2014 at 08:17:11PM -0700, Linus Torvalds wrote:
> In other words, I'll happily pull this, but your excuses for it are
> wrong-headed. There is no "crazyness justifies this". That's crap. But
> the argument of "nobody does this, so let's fix it before anybody
> _starts_ doing it" is perfectly valid - with the deep and implicit
> understanding that if it turns out somebody *does* do it, the change
> gets reverted asap.
Yeap, that's the intention which I failed to articulate. It's highly
unlikely to be in use currently and would already be noticeably
breaking things. Given that it's justified to try to ban '\n' usage
and see whether anybody reports regression from that. Will describe
similar situations more accruately from now on.
Thanks.
--
tejun
prev parent reply other threads:[~2014-09-08 4:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 1:20 [GIT PULL] cgroup fixes for v3.17-rc4 Tejun Heo
[not found] ` <20140908012025.GF5061-9pTldWuhBndy/B6EtB590w@public.gmane.org>
2014-09-08 3:17 ` Linus Torvalds
[not found] ` <CA+55aFw+L1EUDEmAATDtGj_ngHos842jHLddAszboRy4b0pn2A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-08 4:50 ` Tejun Heo [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=20140908045054.GA8526@mtj.dyndns.org \
--to=tj-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.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