diff for duplicates of <48846920-4244-763c-a23b-44f42ac2c2c6@suse.de>

diff --git a/a/1.txt b/N1/1.txt
index 3b6339e..e1dc323 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -6,12 +6,12 @@ On 12/19/2017 09:30 PM, Ray Strode wrote:
 >> reserving the entirety of video RAM, and thus fail loading. This cannot be fixed.
 > well the fix there is to use drm devices... like this:
 > 
-> https://cgit.freedesktop.org/plymouth/commit/?id=97f02ee959374afb1b8a78dc67116cd880cf2d23
+> https://cgit.freedesktop.org/plymouth/commit/?id—f02ee959374afb1b8a78dc67116cd880cf2d23
 
 Sorry, you're confusing things. Please re-read the v1 cover letter, the commit message for patch 1, and the associated discussions.
 
 There is also a bug report where I've described what happens - I think it clarifies the situation a lot:
-  https://bugzilla.opensuse.org/show_bug.cgi?id=980750
+  https://bugzilla.opensuse.org/show_bug.cgi?id˜0750
 
 
 To summarise: What you mean is for Plymouth to ignore FB devices when they have equivalent DRM devices. And yes, Plymouth does that just fine.
diff --git a/a/content_digest b/N1/content_digest
index da4ccf7..5736dc7 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -17,22 +17,22 @@
   "Subject\0Re: [RFC PATCH v2 00/13] Kernel based bootsplash\0"
 ]
 [
-  "Date\0Wed, 20 Dec 2017 14:03:20 +0100\0"
+  "Date\0Wed, 20 Dec 2017 13:03:20 +0000\0"
 ]
 [
   "To\0Ray Strode <halfline\@gmail.com>\0"
 ]
 [
-  "Cc\0b.zolnierkie\@samsung.com",
-  " linux-fbdev\@vger.kernel.org",
+  "Cc\0linux-fbdev\@vger.kernel.org",
   " michal\@markovi.net",
+  " b.zolnierkie\@samsung.com",
   " sndirsch\@suse.com",
   " oneukum\@suse.com",
   " tiwai\@suse.com",
   " dri-devel\@lists.freedesktop.org",
   " Linux-Kernel\@vger. Kernel. Org <linux-kernel\@vger.kernel.org>",
-  " bernhard.rosenkranzer\@linaro.org",
-  " philm\@manjaro.org\0"
+  " philm\@manjaro.org",
+  " bernhard.rosenkranzer\@linaro.org\0"
 ]
 [
   "\0000:1\0"
@@ -49,12 +49,12 @@
   ">> reserving the entirety of video RAM, and thus fail loading. This cannot be fixed.\n",
   "> well the fix there is to use drm devices... like this:\n",
   "> \n",
-  "> https://cgit.freedesktop.org/plymouth/commit/?id=97f02ee959374afb1b8a78dc67116cd880cf2d23\n",
+  "> https://cgit.freedesktop.org/plymouth/commit/?id\342\200\224f02ee959374afb1b8a78dc67116cd880cf2d23\n",
   "\n",
   "Sorry, you're confusing things. Please re-read the v1 cover letter, the commit message for patch 1, and the associated discussions.\n",
   "\n",
   "There is also a bug report where I've described what happens - I think it clarifies the situation a lot:\n",
-  "  https://bugzilla.opensuse.org/show_bug.cgi?id=980750\n",
+  "  https://bugzilla.opensuse.org/show_bug.cgi?id\313\2340750\n",
   "\n",
   "\n",
   "To summarise: What you mean is for Plymouth to ignore FB devices when they have equivalent DRM devices. And yes, Plymouth does that just fine.\n",
@@ -203,4 +203,4 @@
   "Max"
 ]
 
-d31bc1558a498a00ab1fef629df40d1bb48f7f969a95ebcc362467c0a1726fcb
+af96ee379598398649fd6d78a33d434f6f4b37590b2a28b7067c53bbee9e5ad3
