All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <55F9BB79.20203@users.sourceforge.net>

diff --git a/a/1.txt b/N1/1.txt
index c7b86fa..82ec8c6 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -5,7 +5,7 @@ I find that such a design decision will need more fine-tuning of the suggested
 small SmPL script.
 
 
-> + at r depends on context || org || report@
+> +@r depends on context || org || report@
 > +position p;
 > +typedef u8, u16, u32, u64;
 > +{unsigned char, unsigned short int, unsigned int, unsigned long, unsigned long long, size_t, u8, u16, u32, u64} v;
@@ -16,9 +16,9 @@ Is it eventually needed to mention the key word "int" also together with the "lo
 > +@@
 > +
 > +(
-> +*v at p < 0
+> +*v@p < 0
 > +|
-> +*v at p >= 0
+> +*v@p >= 0
 > +)
 
 How do you think about to split this SmPL rule so that corresponding warning
diff --git a/a/content_digest b/N1/content_digest
index a969583..9a00952 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,8 +1,8 @@
  "ref\0alpine.DEB.2.10.1509161125370.2429@hadrien\0"
  "ref\01442409749-32700-1-git-send-email-a.hajda@samsung.com\0"
- "From\0elfring@users.sourceforge.net (SF Markus Elfring)\0"
- "Subject\0[Cocci] [PATCH v2] coccinelle: tests: unsigned value cannot be lesser than zero\0"
- "Date\0Wed, 16 Sep 2015 20:56:57 +0200\0"
+ "From\0SF Markus Elfring <elfring@users.sourceforge.net>\0"
+ "Subject\0Re: [PATCH v2] coccinelle: tests: unsigned value cannot be lesser than zero\0"
+ "Date\0Wed, 16 Sep 2015 18:56:57 +0000\0"
  "To\0cocci@systeme.lip6.fr\0"
  "\00:1\0"
  "b\0"
@@ -13,7 +13,7 @@
  "small SmPL script.\n"
  "\n"
  "\n"
- "> + at r depends on context || org || report@\n"
+ "> +@r depends on context || org || report@\n"
  "> +position p;\n"
  "> +typedef u8, u16, u32, u64;\n"
  "> +{unsigned char, unsigned short int, unsigned int, unsigned long, unsigned long long, size_t, u8, u16, u32, u64} v;\n"
@@ -24,9 +24,9 @@
  "> +@@\n"
  "> +\n"
  "> +(\n"
- "> +*v at p < 0\n"
+ "> +*v@p < 0\n"
  "> +|\n"
- "> +*v at p >= 0\n"
+ "> +*v@p >= 0\n"
  "> +)\n"
  "\n"
  "How do you think about to split this SmPL rule so that corresponding warning\n"
@@ -35,4 +35,4 @@
  "Regards,\n"
  Markus
 
-774ed88896c3a9894294f5061207ca385cddafafa348b448aeb5e28018f76d84
+fc925f819916cbc1c80c37459050c8f0238aa51c1c4731fea5cfa9121696dc38

diff --git a/a/1.txt b/N2/1.txt
index c7b86fa..82ec8c6 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -5,7 +5,7 @@ I find that such a design decision will need more fine-tuning of the suggested
 small SmPL script.
 
 
-> + at r depends on context || org || report@
+> +@r depends on context || org || report@
 > +position p;
 > +typedef u8, u16, u32, u64;
 > +{unsigned char, unsigned short int, unsigned int, unsigned long, unsigned long long, size_t, u8, u16, u32, u64} v;
@@ -16,9 +16,9 @@ Is it eventually needed to mention the key word "int" also together with the "lo
 > +@@
 > +
 > +(
-> +*v at p < 0
+> +*v@p < 0
 > +|
-> +*v at p >= 0
+> +*v@p >= 0
 > +)
 
 How do you think about to split this SmPL rule so that corresponding warning
diff --git a/a/content_digest b/N2/content_digest
index a969583..1a5493e 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -1,9 +1,17 @@
  "ref\0alpine.DEB.2.10.1509161125370.2429@hadrien\0"
  "ref\01442409749-32700-1-git-send-email-a.hajda@samsung.com\0"
- "From\0elfring@users.sourceforge.net (SF Markus Elfring)\0"
- "Subject\0[Cocci] [PATCH v2] coccinelle: tests: unsigned value cannot be lesser than zero\0"
+ "From\0SF Markus Elfring <elfring@users.sourceforge.net>\0"
+ "Subject\0Re: [PATCH v2] coccinelle: tests: unsigned value cannot be lesser than zero\0"
  "Date\0Wed, 16 Sep 2015 20:56:57 +0200\0"
- "To\0cocci@systeme.lip6.fr\0"
+ "To\0Andrzej Hajda <a.hajda@samsung.com>\0"
+ "Cc\0Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>"
+  Joe Perches <joe@perches.com>
+  Gilles Muller <Gilles.Muller@lip6.fr>
+  Michal Marek <mmarek@suse.com>
+  Nicolas Palix <nicolas.palix@imag.fr>
+  cocci@systeme.lip6.fr
+  linux-kernel@vger.kernel.org
+ " kernel-janitors@vger.kernel.org\0"
  "\00:1\0"
  "b\0"
  "> As we discussed earlier I have dropped idea of adding v <= 0 as it is widely\n"
@@ -13,7 +21,7 @@
  "small SmPL script.\n"
  "\n"
  "\n"
- "> + at r depends on context || org || report@\n"
+ "> +@r depends on context || org || report@\n"
  "> +position p;\n"
  "> +typedef u8, u16, u32, u64;\n"
  "> +{unsigned char, unsigned short int, unsigned int, unsigned long, unsigned long long, size_t, u8, u16, u32, u64} v;\n"
@@ -24,9 +32,9 @@
  "> +@@\n"
  "> +\n"
  "> +(\n"
- "> +*v at p < 0\n"
+ "> +*v@p < 0\n"
  "> +|\n"
- "> +*v at p >= 0\n"
+ "> +*v@p >= 0\n"
  "> +)\n"
  "\n"
  "How do you think about to split this SmPL rule so that corresponding warning\n"
@@ -35,4 +43,4 @@
  "Regards,\n"
  Markus
 
-774ed88896c3a9894294f5061207ca385cddafafa348b448aeb5e28018f76d84
+5e2cd88c85bbaa7fcca1a5de2450415dc0866b760b697e655005797af5acbb6c

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.