linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Dan Williams <dan.j.williams@intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Karel Zak <kzak@redhat.com>, Linux-MM <linux-mm@kvack.org>,
	Michal Hocko <mhocko@kernel.org>, Michal Hocko <mhocko@suse.com>,
	mm-commits@vger.kernel.org, ndfont@gmail.com, pbadari@us.ibm.com,
	Rafael Wysocki <rafael@kernel.org>,
	rcj@linux.vnet.ibm.com, stable <stable@vger.kernel.org>,
	steve.scargall@intel.com
Subject: Re: [patch 2/5] drivers/base/memory.c: indicate all memory blocks as removable
Date: Wed, 1 Apr 2020 17:40:01 +0200	[thread overview]
Message-ID: <e4c0971c-44b5-644f-2c6d-87cc45840d10@redhat.com> (raw)
In-Reply-To: <20200401153359.bh5vsko6d7ph7y7r@chatter.i7.local>

On 01.04.20 17:33, Konstantin Ryabitsev wrote:
> On Wed, Apr 01, 2020 at 03:35:01PM +0200, David Hildenbrand wrote:
>>>> We would either need to switch Andrew to a set of tools that handle 
>>>> 7bit legacy formats better, or figure out how you can send things 
>>>> via MTAs that won't convert from 8bit to quoted-printable. Maybe 
>>>> you can convince Red Hat to set up their relays to always preserve 
>>>> 8bit?
>>>
>>> I'll give it a try, but I think it's rather unlikely ... :)
>>
>> So, people are looking into. Literally any mail that goes via Mimecast
>> servers (at least sent by me!) is converted *for whatever reason* to
>> quoted-printable.
> 
> I mean, it's not *wrong* to do that -- older mail standards required 
> that all MTA-to-MTA communication should be done in 7bit. But we're 
> literally talking previous-century legacy protocols here. Forcefully 
> converting all mail to 7bit is about the most 90s thing you can do these 
> days, short of being really into mullets and Arsenio Hall.

The last sentence really made my day, thanks :D

> 
>> E.g., patches I punched out today via "git send-email" even have the
>> line continuations thingy again (they disappeared for a while, maybe
>> there are different MTAs involved and it's like playing the lottery)
> 
> Those show up when your lines are longer than 76 characters. Because, 
> you know, otherwise the message would be too wide to fit through the 
> ethernet cable.

Yeah, however, the mail servers I'm using are not doing this
consistently. Maybe some of them are more advanced than others :)

Let's see if IT can teach these mail servers about the 21 century ...

-- 
Thanks,

David / dhildenb



  reply	other threads:[~2020-04-01 15:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-29  2:14 incoming Andrew Morton
2020-03-29  2:17 ` [patch 1/5] mm/swapfile.c: move inode_lock out of claim_swapfile Andrew Morton
2020-03-29  2:17 ` [patch 2/5] drivers/base/memory.c: indicate all memory blocks as removable Andrew Morton
2020-03-29 16:46   ` Linus Torvalds
2020-03-29 18:03     ` David Hildenbrand
2020-03-29 18:28       ` Linus Torvalds
2020-03-29 19:11         ` David Hildenbrand
2020-03-29 19:15           ` Linus Torvalds
2020-03-29 19:43       ` Konstantin Ryabitsev
2020-03-29 19:55         ` Linus Torvalds
2020-03-29 19:56           ` Linus Torvalds
2020-03-30 14:46           ` Konstantin Ryabitsev
2020-03-30 14:54         ` David Hildenbrand
2020-04-01 13:35           ` David Hildenbrand
2020-04-01 15:33             ` Konstantin Ryabitsev
2020-04-01 15:40               ` David Hildenbrand [this message]
2020-03-29  2:17 ` [patch 3/5] hugetlb_cgroup: fix illegal access to memory Andrew Morton
2020-03-29  2:17 ` [patch 4/5] mm: fork: fix kernel_stack memcg stats for various stack implementations Andrew Morton
2020-03-29 16:41   ` Linus Torvalds
2020-03-29  2:17 ` [patch 5/5] mm/sparse: fix kernel crash with pfn_section_valid check Andrew Morton

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=e4c0971c-44b5-644f-2c6d-87cc45840d10@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=kzak@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=mhocko@suse.com \
    --cc=mm-commits@vger.kernel.org \
    --cc=ndfont@gmail.com \
    --cc=pbadari@us.ibm.com \
    --cc=rafael@kernel.org \
    --cc=rcj@linux.vnet.ibm.com \
    --cc=stable@vger.kernel.org \
    --cc=steve.scargall@intel.com \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: [patch 2/5] drivers/base/memory.c: indicate all memory blocks as removable' \
    /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

This is a public inbox, see mirroring instructions
on how to clone and mirror all data and code used for this inbox