diff for duplicates of <1471888542.3746.70.camel@perches.com> diff --git a/a/1.txt b/N1/1.txt index c7217be..a2ecfa9 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -18,7 +18,7 @@ Hi again James. > > > > and that would work regardless of lustre's layout > > in staging or elsewhere. -> I didn't expect this to be requested at this time. I thought this would be? +> I didn't expect this to be requested at this time. I thought this would be > addressed just before we left staging. Sooner is better to me, but that's up to you all. @@ -28,7 +28,7 @@ Sooner is better to me, but that's up to you all. > the staging/lustre/lustre/include/* to include/linux/lustre is pretty > straight forward for the internal kernel headers. > -> The issues is that we still have entanglement issues with some of our uapi? +> The issues is that we still have entanglement issues with some of our uapi > headers with internals of the kernel leaking to userland. Identifying the u_int_<size> and __u<size> types in the code @@ -42,6 +42,6 @@ It's just a code reading convenience to me. > This Wednsday we have a lustre community conference call were we discuss -> upstream issues. This will need to be discussed.?? +> upstream issues. This will need to be discussed. Enjoy. diff --git a/a/content_digest b/N1/content_digest index bc68ebc..aaf8571 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -4,7 +4,7 @@ "ref\01471636905.3893.40.camel@perches.com\0" "ref\0alpine.LFD.2.20.1608221810590.9872@casper.infradead.org\0" "From\0Joe Perches <joe@perches.com>\0" - "Subject\0[lustre-devel] [PATCH 0/7] staging: lustre: last missing patches for lustre 2.6\0" + "Subject\0Re: [PATCH 0/7] staging: lustre: last missing patches for lustre 2.6\0" "Date\0Mon, 22 Aug 2016 10:55:42 -0700\0" "To\0James Simmons <jsimmons@infradead.org>\0" "Cc\0Greg Kroah-Hartman <gregkh@linuxfoundation.org>" @@ -35,7 +35,7 @@ "> > \n" "> > and that would work regardless of lustre's layout\n" "> > in staging or elsewhere.\n" - "> I didn't expect this to be requested at this time. I thought this would be?\n" + "> I didn't expect this to be requested at this time. I thought this would be\302\240\n" "> addressed just before we left staging.\n" "\n" "Sooner is better to me, but that's up to you all.\n" @@ -45,7 +45,7 @@ "> the staging/lustre/lustre/include/* to include/linux/lustre is pretty\n" "> straight forward for the internal kernel headers.\n" "> \n" - "> The issues is that we still have entanglement issues with some of our uapi?\n" + "> The issues is that we still have entanglement issues with some of our uapi\302\240\n" "> headers with internals of the kernel leaking to userland.\n" "\n" "Identifying the u_int_<size> and __u<size> types in the code\n" @@ -59,8 +59,8 @@ "\n" "\n" "> This Wednsday we have a lustre community conference call were we discuss\n" - "> upstream issues. This will need to be discussed.??\n" + "> upstream issues. This will need to be discussed.\302\240\302\240\n" "\n" Enjoy. -df31157960b37eefb8ef8b1dee8beca31d781ed97666ecb24cfad54e6486b067 +757c91554d8f284331d1e23d9b446cbbdad7b6d14e18ff1298301a286970898e
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.