bug#35841: PING: [PATCH v3] IBM Z DFLTCC: fix three data corruption issues

2020-01-10 Thread Jim Meyering
On Fri, Jan 10, 2020 at 3:48 AM Ilya Leoshkevich wrote: > On Sun, 2020-01-05 at 13:12 -0800, Jim Meyering wrote: > > On Tue, Aug 6, 2019 at 2:07 AM Ilya Leoshkevich > > wrote: > > > I would like to ping this patch. > > > > Thanks for your patience. > > I'm prepared to push the attached. > > Pleas

bug#35841: PING: [PATCH v3] IBM Z DFLTCC: fix three data corruption issues

2020-01-10 Thread Ilya Leoshkevich
On Sun, 2020-01-05 at 13:12 -0800, Jim Meyering wrote: > On Tue, Aug 6, 2019 at 2:07 AM Ilya Leoshkevich > wrote: > > I would like to ping this patch. > > Thanks for your patience. > I'm prepared to push the attached. > Please proofread the commit log, noting that I've included this > paragraph:

bug#35841: PING: [PATCH v3] IBM Z DFLTCC: fix three data corruption issues

2020-01-05 Thread Jim Meyering
On Tue, Aug 6, 2019 at 2:07 AM Ilya Leoshkevich wrote: > I would like to ping this patch. Thanks for your patience. I'm prepared to push the attached. Please proofread the commit log, noting that I've included this paragraph: > SUSE maintainers have found an issue related to building zlib in 31-

bug#35841: PING: [PATCH v3] IBM Z DFLTCC: fix three data corruption issues

2019-08-06 Thread Ilya Leoshkevich
Hello, I would like to ping this patch. Also, Paul asked me to document the new environment variables, I’ve also sent a patch for that a while ago: https://lists.gnu.org/archive/html/bug-gzip/2019-04/msg00013.html Best regards, Ilya > Am 08.07.2019 um 15:42 schrieb Ilya Leoshkevich : > > Hell