diff for duplicates of <20160915100759.GA21307@kroah.com> diff --git a/a/1.txt b/N1/1.txt index 009df9d..2d897f8 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -56,7 +56,7 @@ On Thu, Sep 15, 2016 at 08:51:34AM +0000, Joakim Tjernlund wrote: > > > > > > > > > 0003-thinkpad_acpi-Remove-ambiguous-logging-for-Unsupport.patch: > > > > > > > > > 85342b97c2ee2a94a31ea5d59d58cdfd1f045e2a > > > > > > > > -> > > > > > > > Nor this one. I stopped here, assuming that your other ids aren't +> > > > > > > > Nor this one.��I stopped here, assuming that your other ids aren't > > > > > > > > correct either :( > > > > > > > > > > > > > > > > > @@ -75,7 +75,7 @@ On Thu, Sep 15, 2016 at 08:51:34AM +0000, Joakim Tjernlund wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > And what happened to the other patches in this series? -> > > > > > > > > > +> > > > > > > > > > � > > > > > > > > > The first one was inappropriate, that is why 0001 is missing. > > > > > > > > > > > > > > > > That's pretty strange of you to force us to guess what is going on here, @@ -88,21 +88,21 @@ On Thu, Sep 15, 2016 at 08:51:34AM +0000, Joakim Tjernlund wrote: > > > > > > > I cannot figure out how generate a series from commits that are non sequential in Linux tree. > > > > > > > git format path does not have a syntax for that from what I can tell, any ideas? > > > > > > -> > > > > > Why not just send us the git commit ids that you want applied? That's +> > > > > > Why not just send us the git commit ids that you want applied?��That's > > > > > > all we need. -> > > > > > +> > > > > > � > > > > > Oh, didn't occur to me. Here we go(ltes se fi I got it right this time :) > > > > > -> > > > > bb28f3d51ff5e1be541d057708011cc1efe6fae9 - thinkpad_acpi: Add support for keyboard backlight +> > > > > bb28f3d51ff5e1be541d057708011cc1efe6fae9 -�thinkpad_acpi: Add support for keyboard backlight > > > > > > > > How does this commit meet the Documentation/stable_kernel_rules.txt -> > > > requirements? It's a new feature, and too big, why would we add it to -> > > > an old kernel like this one? What's wrong with just using a newer +> > > > requirements?��It's a new feature, and too big, why would we add it to +> > > > an old kernel like this one?��What's wrong with just using a newer > > > > kernel for a feature like this? > > > > > > > > > > > > > > -> > > > > 15c75626f0999cce8357c8bf8578247134032acb - thinkpad_acpi: Remove ambiguous logging for "Unsupported +> > > > > 15c75626f0999cce8357c8bf8578247134032acb -�thinkpad_acpi: Remove ambiguous logging for "Unsupported > > > > > brightness interface" > > > > > a7718360d91eedbedd58978ec8fff4a67a866f86 - thinkpad_acpi: Silence an uninitialized variable warning > > > > > afcedebc6a094224973534f43b396bbbf33fe44e - thinkpad_acpi: save kbdlight state on suspend and restore @@ -134,8 +134,8 @@ and device id additions, yes we do. But this involves new code and functions and really, a new feature implemented for that hardware. > > > The other patches were just there to make sure I didn't run inte -> > > conflicts I didn't want to resolve. They all made sense except for -> > > maybe the one adding keyboard backlight. +> > > conflicts I didn't want to resolve.��They all made sense except for +> > > maybe the one adding keyboard backlight.� > > > > > > > > > > > And why aren't we cc:ing the maintainers of this subsystem? @@ -144,8 +144,8 @@ functions and really, a new feature implemented for that hardware. > > > inappropriate for stable I will just carry them my self until the next > > > major stable kernel is released. > > -> > What is wrong with 4.7-stable kernels? Why are you "stuck" at 4.4? -> > +> > What is wrong with 4.7-stable kernels?��Why are you "stuck" at 4.4? +> >� > > Non LTS kernels are fairly short lived. First you have wait for a few > patch levels(say >=5) before one can consider the kernel fairly @@ -156,7 +156,7 @@ bugfixes that are in Linus's tree, not that were specifically for that stable kernel release alone. > After that there isn't that many release before it retired and you -> have to look for the next stable kernel. +> have to look for the next stable kernel.� Yes, it's a never ending treadmill, welcome to the real world :) diff --git a/a/content_digest b/N1/content_digest index b37fefc..1578d33 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -75,7 +75,7 @@ "> > > > > > > > > 0003-thinkpad_acpi-Remove-ambiguous-logging-for-Unsupport.patch:\n" "> > > > > > > > > 85342b97c2ee2a94a31ea5d59d58cdfd1f045e2a\n" "> > > > > > > > \n" - "> > > > > > > > Nor this one.\302\240\302\240I stopped here, assuming that your other ids aren't\n" + "> > > > > > > > Nor this one.\303\257\302\277\302\275\303\257\302\277\302\275I stopped here, assuming that your other ids aren't\n" "> > > > > > > > correct either :(\n" "> > > > > > > > \n" "> > > > > > > > > \n" @@ -94,7 +94,7 @@ "> > > > > > > > > > \n" "> > > > > > > > > > \n" "> > > > > > > > > > And what happened to the other patches in this series?\n" - "> > > > > > > > > > \302\240\n" + "> > > > > > > > > > \303\257\302\277\302\275\n" "> > > > > > > > > The first one was inappropriate, that is why 0001 is missing.\n" "> > > > > > > > \n" "> > > > > > > > That's pretty strange of you to force us to guess what is going on here,\n" @@ -107,21 +107,21 @@ "> > > > > > > I cannot figure out how generate a series from commits that are non sequential in Linux tree.\n" "> > > > > > > git format path does not have a syntax for that from what I can tell, any ideas?\n" "> > > > > > \n" - "> > > > > > Why not just send us the git commit ids that you want applied?\302\240\302\240That's\n" + "> > > > > > Why not just send us the git commit ids that you want applied?\303\257\302\277\302\275\303\257\302\277\302\275That's\n" "> > > > > > all we need.\n" - "> > > > > > \302\240\n" + "> > > > > > \303\257\302\277\302\275\n" "> > > > > Oh, didn't occur to me. Here we go(ltes se fi I got it right this time :)\n" "> > > > > \n" - "> > > > > bb28f3d51ff5e1be541d057708011cc1efe6fae9 -\302\240thinkpad_acpi: Add support for keyboard backlight\n" + "> > > > > bb28f3d51ff5e1be541d057708011cc1efe6fae9 -\303\257\302\277\302\275thinkpad_acpi: Add support for keyboard backlight\n" "> > > > \n" "> > > > How does this commit meet the Documentation/stable_kernel_rules.txt\n" - "> > > > requirements?\302\240\302\240It's a new feature, and too big, why would we add it to\n" - "> > > > an old kernel like this one?\302\240\302\240What's wrong with just using a newer\n" + "> > > > requirements?\303\257\302\277\302\275\303\257\302\277\302\275It's a new feature, and too big, why would we add it to\n" + "> > > > an old kernel like this one?\303\257\302\277\302\275\303\257\302\277\302\275What's wrong with just using a newer\n" "> > > > kernel for a feature like this?\n" "> > > > \n" "> > > > > \n" "> > > > > \n" - "> > > > > 15c75626f0999cce8357c8bf8578247134032acb -\302\240thinkpad_acpi: Remove ambiguous logging for \"Unsupported\n" + "> > > > > 15c75626f0999cce8357c8bf8578247134032acb -\303\257\302\277\302\275thinkpad_acpi: Remove ambiguous logging for \"Unsupported\n" "> > > > > brightness interface\"\n" "> > > > > a7718360d91eedbedd58978ec8fff4a67a866f86 - thinkpad_acpi: Silence an uninitialized variable warning\n" "> > > > > afcedebc6a094224973534f43b396bbbf33fe44e - thinkpad_acpi: save kbdlight state on suspend and restore\n" @@ -153,8 +153,8 @@ "functions and really, a new feature implemented for that hardware.\n" "\n" "> > > The other patches were just there to make sure I didn't run inte\n" - "> > > conflicts I didn't want to resolve.\302\240\302\240They all made sense except for\n" - "> > > maybe the one adding keyboard backlight.\302\240\n" + "> > > conflicts I didn't want to resolve.\303\257\302\277\302\275\303\257\302\277\302\275They all made sense except for\n" + "> > > maybe the one adding keyboard backlight.\303\257\302\277\302\275\n" "> > > \n" "> > > > \n" "> > > > And why aren't we cc:ing the maintainers of this subsystem?\n" @@ -163,8 +163,8 @@ "> > > inappropriate for stable I will just carry them my self until the next\n" "> > > major stable kernel is released.\n" "> > \n" - "> > What is wrong with 4.7-stable kernels?\302\240\302\240Why are you \"stuck\" at 4.4?\n" - "> >\302\240\n" + "> > What is wrong with 4.7-stable kernels?\303\257\302\277\302\275\303\257\302\277\302\275Why are you \"stuck\" at 4.4?\n" + "> >\303\257\302\277\302\275\n" "> \n" "> Non LTS kernels are fairly short lived. First you have wait for a few\n" "> patch levels(say >=5) before one can consider the kernel fairly\n" @@ -175,7 +175,7 @@ "stable kernel release alone.\n" "\n" "> After that there isn't that many release before it retired and you\n" - "> have to look for the next stable kernel.\302\240\n" + "> have to look for the next stable kernel.\303\257\302\277\302\275\n" "\n" "Yes, it's a never ending treadmill, welcome to the real world :)\n" "\n" @@ -211,4 +211,4 @@ "\n" greg k-h -dafaa4d12f07d84c47d747f60ecfc3062287b16f4ec009000b99f5e5184eaf77 +9959bb929809444b80863e05d5ec4c47a5454d75dc50fd7afb32b13d3d4ab097
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.