All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20160114225850.GA23382@cmpxchg.org>

diff --git a/a/1.txt b/N1/1.txt
index 6fca34d..a10e43c 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -32,9 +32,3 @@ it's silly to panic while there are still killable tasks available.
 Hence my proposal to wait a decaying amount of time after each OOM
 victim before moving on, until we killed everything in the system and
 panic (and reboot). What else is there we can do once out of memory?
-
---
-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>
diff --git a/a/content_digest b/N1/content_digest
index 8f54ac8..a67675b 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -55,12 +55,6 @@
  "\n"
  "Hence my proposal to wait a decaying amount of time after each OOM\n"
  "victim before moving on, until we killed everything in the system and\n"
- "panic (and reboot). What else is there we can do once out of memory?\n"
- "\n"
- "--\n"
- "To unsubscribe, send a message with 'unsubscribe linux-mm' in\n"
- "the body to majordomo@kvack.org.  For more info on Linux MM,\n"
- "see: http://www.linux-mm.org/ .\n"
- "Don't email: <a href=mailto:\"dont@kvack.org\"> email@kvack.org </a>"
+ panic (and reboot). What else is there we can do once out of memory?
 
-85786f753bb5555e6e94eb76adae5116d29144a90e0ac0f2bb3aee095b01f82c
+0555454e97eae06d5cb08c13fd219ecd534c07634cd76d9c11275cddfcd18804

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.