Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail From: L A Walsh Newsgroups: gnu.bash.bug Subject: Re: valid kernel patch? using -e to catch errors? Date: Tue, 30 Jul 2019 00:55:26 -0700 Lines: 27 Approved: bug-bash@gnu.org Message-ID: References: <5D3EA81D.4020308@tlinx.org> <29600.1564465775@jinx.noi.kre.to> <5D3FF7EE.9090207@tlinx.org> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: usenet.stanford.edu 1564473339 23121 209.51.188.17 (30 Jul 2019 07:55:39 GMT) X-Complaints-To: action@cs.stanford.edu Cc: bug-bash To: Robert Elz Envelope-to: bug-bash@gnu.org User-Agent: Thunderbird In-Reply-To: <29600.1564465775@jinx.noi.kre.to> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x (no timestamps) [generic] X-Received-From: 173.164.175.65 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-Mailman-Original-Message-ID: <5D3FF7EE.9090207@tlinx.org> X-Mailman-Original-References: <5D3EA81D.4020308@tlinx.org> <29600.1564465775@jinx.noi.kre.to> Xref: csiph.com gnu.bash.bug:15278 On 2019/07/29 22:49, kre@munnari.OZ.AU wrote: > | I didn't see this come back from the list and it was sent > | 45 minutes ago (vs. other emails of mine that have come > | back in under a minute). > | Did anyone else see it? > > Yes. The original appeared (before this repeat). Avoid > being impatient, all kinds of things can delay e-mail (a once > an hour retry is not uncommon - so 45 mins is certainly not > long enough to wait before becoming concerned - allow at least > a day). > --- Atypical behavior is cause for concern. The list received the posting, but FYI, I still haven't received either post. > | FWIW, the below is from the publicly posted change notes > | for the 5.2.3 patch. > > I have no idea what patch you're talking about, as it has > nothing to do with any system I run. > Then why not ignore it? Why respond to it? You've given it more response feedback than anyone. It's from the kernel patch notes and is from a patch that went into the linux kernel.