All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20180503173422.GR18390@sasha-vm>

diff --git a/a/1.txt b/N1/1.txt
index 7ff9146..92746ef 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -79,3 +79,7 @@ introduce arbitrary rules to make your life miserable.
 >#2.  We can't apply #3 without #1 --- they can be transposed, but
 >it's nowhere near a mechanical transformation.  So WTF should #3
 >have in "Fixes:"?
+_______________________________________________
+Ksummit-discuss mailing list
+Ksummit-discuss@lists.linuxfoundation.org
+https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
diff --git a/a/content_digest b/N1/content_digest
index 1496efd..5474048 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -5,7 +5,7 @@
  "ref\020180503000620.GA29205@thunk.org\0"
  "ref\020180503144612.GJ18390@sasha-vm\0"
  "ref\020180503165446.GB30522@ZenIV.linux.org.uk\0"
- "From\0Sasha Levin <Alexander.Levin@microsoft.com>\0"
+ "From\0Sasha Levin via Ksummit-discuss <ksummit-discuss@lists.linuxfoundation.org>\0"
  "Subject\0Re: [Ksummit-discuss] bug-introducing patches\0"
  "Date\0Thu, 3 May 2018 17:34:24 +0000\0"
  "To\0Al Viro <viro@zeniv.linux.org.uk>\0"
@@ -95,6 +95,10 @@
  ">next one?  We can't apply #1 + #3 --- #3 won't even compile without\n"
  ">#2.  We can't apply #3 without #1 --- they can be transposed, but\n"
  ">it's nowhere near a mechanical transformation.  So WTF should #3\n"
- ">have in \"Fixes:\"?"
+ ">have in \"Fixes:\"?\n"
+ "_______________________________________________\n"
+ "Ksummit-discuss mailing list\n"
+ "Ksummit-discuss@lists.linuxfoundation.org\n"
+ https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
 
-465563ef1ce4011f26f11bdc19a19caec7c71ff56a00dc98e282a390f535df2e
+6b911e5b2b5617faccbde032fe1c5a35e025de860ecdc2115aa4a34f117a18aa

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.