diff for duplicates of <CAMP44s0RohH9tPiM5qCDT57XBV=iO66PZkSjYVxA6Usg1qJPtw@mail.gmail.com>
diff --git a/a/1.txt b/N1/1.txt
index fdb3a2a..e2d86af 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -4,7 +4,7 @@ On Fri, Apr 13, 2012 at 11:57 AM, Stefan Richter
>> But this is exactly the opposite; the patch that broke things is in
>> the 'release branch' (3.3.1); it's not in upstream (3.3). Sure, it's
>> also on a later upstream, which is also broken.
-> ^^^^^
+> ? ? ? ? ? ?^^^^^
> No, upstream /earlier/ than 3.3.1 contains the defect.
Time is not relevant for the point being made, but fine:
@@ -14,10 +14,10 @@ the 'release branch' (3.3.1); it's not in the upstream release from
where stable began (3.3). Sure, it's also on upstream, which is also
broken.
-> Furthermore, consider this: You as user of the 3.3.y series are using a
-> temporary, dead-end side branch. Its maintenance will stop at some point,
+> Furthermore, consider this: ?You as user of the 3.3.y series are using a
+> temporary, dead-end side branch. ?Its maintenance will stop at some point,
> and you will be left looking for a different, maintained series to migrate
-> to. You will be most interested in that series /not/ containing any
+> to. ?You will be most interested in that series /not/ containing any
> regressions that you suffered already through the 3.3.y lifetime.
Of course, I will be interested in that, although most likely I would
diff --git a/a/content_digest b/N1/content_digest
index 904fde6..2ab72a9 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -35,27 +35,13 @@
"From\0Felipe Contreras <felipe.contreras\@gmail.com>\0"
]
[
- "Subject\0Re: [ 00/78] 3.3.2-stable review\0"
+ "Subject\0[ath9k-devel] [ 00/78] 3.3.2-stable review\0"
]
[
"Date\0Fri, 13 Apr 2012 13:29:46 +0300\0"
]
[
- "To\0Stefan Richter <stefanr\@s5r6.in-berlin.de>\0"
-]
-[
- "Cc\0Adrian Chadd <adrian\@freebsd.org>",
- " Greg KH <gregkh\@linuxfoundation.org>",
- " Sergio Correia <lists\@uece.net>",
- " linux-kernel\@vger.kernel.org",
- " stable\@vger.kernel.org",
- " torvalds\@linux-foundation.org",
- " akpm\@linux-foundation.org",
- " alan\@lxorguk.ukuu.org.uk",
- " linux-wireless Mailing List <linux-wireless\@vger.kernel.org>",
- " Sujith Manoharan <c_manoha\@qca.qualcomm.com>",
- " ath9k-devel\@lists.ath9k.org <ath9k-devel\@venema.h4ckr.net>",
- " John W. Linville <linville\@tuxdriver.com>\0"
+ "To\0ath9k-devel\@lists.ath9k.org\0"
]
[
"\0000:1\0"
@@ -70,7 +56,7 @@
">> But this is exactly the opposite; the patch that broke things is in\n",
">> the 'release branch' (3.3.1); it's not in upstream (3.3). Sure, it's\n",
">> also on a later upstream, which is also broken.\n",
- "> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240^^^^^\n",
+ "> ? ? ? ? ? ?^^^^^\n",
"> No, upstream /earlier/ than 3.3.1 contains the defect.\n",
"\n",
"Time is not relevant for the point being made, but fine:\n",
@@ -80,10 +66,10 @@
"where stable began (3.3). Sure, it's also on upstream, which is also\n",
"broken.\n",
"\n",
- "> Furthermore, consider this: \302\240You as user of the 3.3.y series are using a\n",
- "> temporary, dead-end side branch. \302\240Its maintenance will stop at some point,\n",
+ "> Furthermore, consider this: ?You as user of the 3.3.y series are using a\n",
+ "> temporary, dead-end side branch. ?Its maintenance will stop at some point,\n",
"> and you will be left looking for a different, maintained series to migrate\n",
- "> to. \302\240You will be most interested in that series /not/ containing any\n",
+ "> to. ?You will be most interested in that series /not/ containing any\n",
"> regressions that you suffered already through the 3.3.y lifetime.\n",
"\n",
"Of course, I will be interested in that, although most likely I would\n",
@@ -116,4 +102,4 @@
"Felipe Contreras"
]
-d347de2bf3c0b9a25290db2d699ee6336bc4fa4a2e47c829c4a6bc08b637357a
+d1214c807f879ec73803271cd7474ad28c0a6599d1777e8c54ed1a785375316e
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.