diff for duplicates of <515BE8C3.6040205@parallels.com> diff --git a/a/1.txt b/N1/1.txt index aef9f53..08035b3 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -11,7 +11,7 @@ states due to static branches management. This is only important in the first activation, to make sure the static branches patching are synchronized. -From this point on, the ACTIVE flag is the one we should be looking at. +>From this point on, the ACTIVE flag is the one we should be looking at. Again, I fully agree it is complicated, but being that a property of the static branches (we tried to fix it in the static branches itself but diff --git a/a/content_digest b/N1/content_digest index ebca6bf..414bd5f 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -34,7 +34,7 @@ "first activation, to make sure the static branches patching are\n" "synchronized.\n" "\n" - "From this point on, the ACTIVE flag is the one we should be looking at.\n" + ">From this point on, the ACTIVE flag is the one we should be looking at.\n" "\n" "Again, I fully agree it is complicated, but being that a property of the\n" "static branches (we tried to fix it in the static branches itself but\n" @@ -51,4 +51,4 @@ "see: http://www.linux-mm.org/ .\n" "Don't email: <a href=mailto:\"dont@kvack.org\"> email@kvack.org </a>" -2db982cbf61a758d0143e39ba14db636937bdf22f63c55b22f4a1ad9e1e0aa12 +7b36d916832f362732fe2aa3aecfea302a524e47ab08333927267b984bb2dde9
diff --git a/a/1.txt b/N2/1.txt index aef9f53..4c370ec 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -11,7 +11,7 @@ states due to static branches management. This is only important in the first activation, to make sure the static branches patching are synchronized. -From this point on, the ACTIVE flag is the one we should be looking at. +>From this point on, the ACTIVE flag is the one we should be looking at. Again, I fully agree it is complicated, but being that a property of the static branches (we tried to fix it in the static branches itself but @@ -21,9 +21,3 @@ documenting the states as well as I could. But that not always work *that* well. Maybe we can use the results of this discussion to document the tear down process a bit more? - --- -To unsubscribe, send a message with 'unsubscribe linux-mm' in -the body to majordomo@kvack.org. For more info on Linux MM, -see: http://www.linux-mm.org/ . -Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a> diff --git a/a/content_digest b/N2/content_digest index ebca6bf..2ba35bb 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -18,7 +18,7 @@ KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> LKML <linux-kernel@vger.kernel.org> Cgroups <cgroups@vger.kernel.org> - " linux-mm@kvack.org\0" + " <linux-mm@kvack.org>\0" "\00:1\0" "b\0" "On 04/03/2013 12:18 PM, Michal Hocko wrote:\n" @@ -34,7 +34,7 @@ "first activation, to make sure the static branches patching are\n" "synchronized.\n" "\n" - "From this point on, the ACTIVE flag is the one we should be looking at.\n" + ">From this point on, the ACTIVE flag is the one we should be looking at.\n" "\n" "Again, I fully agree it is complicated, but being that a property of the\n" "static branches (we tried to fix it in the static branches itself but\n" @@ -43,12 +43,6 @@ "documenting the states as well as I could.\n" "\n" "But that not always work *that* well. Maybe we can use the results of\n" - "this discussion to document the tear down process a bit more?\n" - "\n" - "--\n" - "To unsubscribe, send a message with 'unsubscribe linux-mm' in\n" - "the body to majordomo@kvack.org. For more info on Linux MM,\n" - "see: http://www.linux-mm.org/ .\n" - "Don't email: <a href=mailto:\"dont@kvack.org\"> email@kvack.org </a>" + this discussion to document the tear down process a bit more? -2db982cbf61a758d0143e39ba14db636937bdf22f63c55b22f4a1ad9e1e0aa12 +c149d880d6fd380f3d19f07a34036a334b61c0a56fca883f03dcc773dbd25912
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.