diff for duplicates of <53CF7191.2090008@canonical.com>

diff --git a/a/1.txt b/N1/1.txt
index a36c78e..9ae9a0e 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -19,8 +19,3 @@ op 23-07-14 10:20, Christian König schreef:
 In this case if the sync was to i915 the i915 lockup procedure would take care of itself. It wouldn't fix radeon, but it would at least unblock your intel card again. I haven't specifically added a special case to attempt to unblock external fences, but I've considered it. :-)
 
 ~Maarten
-
-_______________________________________________
-Nouveau mailing list
-Nouveau@lists.freedesktop.org
-http://lists.freedesktop.org/mailman/listinfo/nouveau
diff --git a/a/content_digest b/N1/content_digest
index 09afadc..db167b5 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -21,20 +21,19 @@
  "ref\053CF6B18.5070107@vodafone.de\0"
  "ref\0CAKMK7uGd65HR11thcv8KjDw-RnTa7W-QGOzFGFd+oO_hp8wyHA@mail.gmail.com\0"
  "ref\053CF7035.2060808@amd.com\0"
- "ref\053CF7035.2060808-5C7GfCeVMHo@public.gmane.org\0"
- "From\0Maarten Lankhorst <maarten.lankhorst-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>\0"
- "Subject\0Re: [PATCH 09/17] drm/radeon: use common fence implementation for fences\0"
+ "From\0Maarten Lankhorst <maarten.lankhorst@canonical.com>\0"
+ "Subject\0Re: [Nouveau] [PATCH 09/17] drm/radeon: use common fence implementation for fences\0"
  "Date\0Wed, 23 Jul 2014 10:25:53 +0200\0"
- "To\0Christian K\303\266nig <christian.koenig-5C7GfCeVMHo@public.gmane.org>"
-  Daniel Vetter <daniel.vetter-/w4YWyX8dFk@public.gmane.org>
- " Christian K\303\266nig <deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>\0"
- "Cc\0Thomas Hellstrom <thellstrom-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>"
-  nouveau <nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
-  LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
-  dri-devel <dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
-  Ben Skeggs <bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
+ "To\0Christian K\303\266nig <christian.koenig@amd.com>"
+  Daniel Vetter <daniel.vetter@ffwll.ch>
+ " Christian K\303\266nig <deathsimple@vodafone.de>\0"
+ "Cc\0Thomas Hellstrom <thellstrom@vmware.com>"
+  nouveau <nouveau@lists.freedesktop.org>
+  LKML <linux-kernel@vger.kernel.org>
+  dri-devel <dri-devel@lists.freedesktop.org>
+  Ben Skeggs <bskeggs@redhat.com>
   Deucher
- " Alexander <alexander.deucher-5C7GfCeVMHo@public.gmane.org>\0"
+ " Alexander <alexander.deucher@amd.com>\0"
  "\00:1\0"
  "b\0"
  "op 23-07-14 10:20, Christian K\303\266nig schreef:\n"
@@ -57,11 +56,6 @@
  "> An additional problem here is that resets are something perfect normal for radeon. For example UVD can \"crash\" when you feed it with invalid bitstream data, (ok actually it send an interrupt and stops any processing for the driver to investigate). To continue processing you need to go through a rather complicated reset procedure.\n"
  "In this case if the sync was to i915 the i915 lockup procedure would take care of itself. It wouldn't fix radeon, but it would at least unblock your intel card again. I haven't specifically added a special case to attempt to unblock external fences, but I've considered it. :-)\n"
  "\n"
- "~Maarten\n"
- "\n"
- "_______________________________________________\n"
- "Nouveau mailing list\n"
- "Nouveau@lists.freedesktop.org\n"
- http://lists.freedesktop.org/mailman/listinfo/nouveau
+ ~Maarten
 
-64b2959d9bf8b7d73049318b00bdc01b2edfbeb9c570eafe44e579003678f499
+225dc6e8118c569c804a47807a2d5b57b2009da5debdce739309bfcc1ccf4c39
