diff for duplicates of <20200219183841.GA54486@cmpxchg.org>

diff --git a/a/1.txt b/N1/1.txt
index 838668e..b40a617 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,5 +1,5 @@
 On Wed, Feb 19, 2020 at 11:28:48AM -0500, Kenny Ho wrote:
-> On Wed, Feb 19, 2020 at 11:18 AM Johannes Weiner <hannes@cmpxchg.org> wrote:
+> On Wed, Feb 19, 2020 at 11:18 AM Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org> wrote:
 > >
 > > Yes, I'd go with absolute units when it comes to memory, because it's
 > > not a renewable resource like CPU and IO, and so we do have cliff
@@ -14,7 +14,7 @@ On Wed, Feb 19, 2020 at 11:28:48AM -0500, Kenny Ho wrote:
 Here is a cleanup patch, not yet merged, that documents the exact
 semantics and behavioral considerations:
 
-https://lore.kernel.org/linux-mm/20191213192158.188939-3-hannes@cmpxchg.org/
+https://lore.kernel.org/linux-mm/20191213192158.188939-3-hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org/
 
 But the high-level idea is this: you assign each cgroup or cgroup
 subtree a chunk of the resource that it's guaranteed to be able to
@@ -32,7 +32,3 @@ varies over time, workloads disappear and new ones start up etc.
 If you implement only one allocation model, the preference would be on
 memory.low. Limits are rigid and per definition waste resources, so in
 practice we're moving away from them.
-_______________________________________________
-amd-gfx mailing list
-amd-gfx@lists.freedesktop.org
-https://lists.freedesktop.org/mailman/listinfo/amd-gfx
diff --git a/a/content_digest b/N1/content_digest
index cc9c7f0..fed7f54 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -7,32 +7,33 @@
  "ref\020200214191754.GA218629@mtj.thefacebook.com\0"
  "ref\020200219161850.GB13406@cmpxchg.org\0"
  "ref\0CAOWid-e=7V4TUqK_h5Gs9dUXqH-Vgr-Go8c1dCkMux98Vdd1sQ@mail.gmail.com\0"
- "From\0Johannes Weiner <hannes@cmpxchg.org>\0"
+ "ref\0CAOWid-e=7V4TUqK_h5Gs9dUXqH-Vgr-Go8c1dCkMux98Vdd1sQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org\0"
+ "From\0Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>\0"
  "Subject\0Re: [PATCH 09/11] drm, cgroup: Introduce lgpu as DRM cgroup resource\0"
  "Date\0Wed, 19 Feb 2020 13:38:41 -0500\0"
- "To\0Kenny Ho <y2kenny@gmail.com>\0"
- "Cc\0juan.zuniga-anaya@amd.com"
-  Daniel Vetter <daniel@ffwll.ch>
-  Kenny Ho <Kenny.Ho@amd.com>
+ "To\0Kenny Ho <y2kenny-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>\0"
+ "Cc\0Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>"
+  Daniel Vetter <daniel-/w4YWyX8dFk@public.gmane.org>
+  Jason Ekstrand <jason-fQELhIk9awXprZlt/sZkLg@public.gmane.org>
+  Kenny Ho <Kenny.Ho-5C7GfCeVMHo@public.gmane.org>
+  cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
+  Maling list - DRI developers <dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
+  amd-gfx mailing list <amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
+  Alex Deucher <alexander.deucher-5C7GfCeVMHo@public.gmane.org>
+ " Christian K\303\266nig <christian.koenig-5C7GfCeVMHo@public.gmane.org>"
   Kuehling
-  Felix <felix.kuehling@amd.com>
-  jsparks@cray.com
-  nirmoy.das@amd.com
-  Maling list - DRI developers <dri-devel@lists.freedesktop.org>
-  lkaplan@cray.com
-  Alex Deucher <alexander.deucher@amd.com>
+  Felix <felix.kuehling-5C7GfCeVMHo@public.gmane.org>
   Greathouse
-  Joseph <joseph.greathouse@amd.com>
-  amd-gfx mailing list <amd-gfx@lists.freedesktop.org>
-  Jason Ekstrand <jason@jlekstrand.net>
-  Tejun Heo <tj@kernel.org>
-  cgroups@vger.kernel.org
- " Christian K\303\266nig <christian.koenig@amd.com>"
- " damon.mcdougall@amd.com\0"
+  Joseph <joseph.greathouse-5C7GfCeVMHo@public.gmane.org>
+  jsparks-WVYJKLFxKCc@public.gmane.org
+  lkaplan-WVYJKLFxKCc@public.gmane.org
+  nirmoy.das-5C7GfCeVMHo@public.gmane.org
+  damon.mcdougall-5C7GfCeVMHo@public.gmane.org
+ " juan.zuniga-anaya-5C7GfCeVMHo@public.gmane.org\0"
  "\00:1\0"
  "b\0"
  "On Wed, Feb 19, 2020 at 11:28:48AM -0500, Kenny Ho wrote:\n"
- "> On Wed, Feb 19, 2020 at 11:18 AM Johannes Weiner <hannes@cmpxchg.org> wrote:\n"
+ "> On Wed, Feb 19, 2020 at 11:18 AM Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org> wrote:\n"
  "> >\n"
  "> > Yes, I'd go with absolute units when it comes to memory, because it's\n"
  "> > not a renewable resource like CPU and IO, and so we do have cliff\n"
@@ -47,7 +48,7 @@
  "Here is a cleanup patch, not yet merged, that documents the exact\n"
  "semantics and behavioral considerations:\n"
  "\n"
- "https://lore.kernel.org/linux-mm/20191213192158.188939-3-hannes@cmpxchg.org/\n"
+ "https://lore.kernel.org/linux-mm/20191213192158.188939-3-hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org/\n"
  "\n"
  "But the high-level idea is this: you assign each cgroup or cgroup\n"
  "subtree a chunk of the resource that it's guaranteed to be able to\n"
@@ -64,10 +65,6 @@
  "\n"
  "If you implement only one allocation model, the preference would be on\n"
  "memory.low. Limits are rigid and per definition waste resources, so in\n"
- "practice we're moving away from them.\n"
- "_______________________________________________\n"
- "amd-gfx mailing list\n"
- "amd-gfx@lists.freedesktop.org\n"
- https://lists.freedesktop.org/mailman/listinfo/amd-gfx
+ practice we're moving away from them.
 
-ad80eb94307a881ba05047f9bf9a73e6e7ad632aedfe92f290650f49d6edf8e2
+8a24f6790a8e2856e4b4626ce80bb4abd32cef61a42abba620259317ab65e199
