From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2345 invoked by alias); 2 Jul 2017 20:05:29 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 41387 Received: (qmail 4539 invoked from network); 2 Jul 2017 20:05:29 -0000 X-Qmail-Scanner-Diagnostics: from mail-qk0-f179.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(209.85.220.179):SA:0(0.5/5.0):. Processed in 1.184403 secs); 02 Jul 2017 20:05:29 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=0.5 required=5.0 tests=RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,RCVD_IN_SORBS_SPAM,SPF_PASS, T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.220.179 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=LS5KkYv/TM+vTP0VYCFvkxZPkYL66FuvkRBR7Z6GFqQ=; b=sQ8A77vmboLsAyo0u1mHCg+wOWRMJzLrNW/nHuev1iJRxzVhmhRLnEZDhh3AOia7zo KQT2+lhRd3N6qYS1++JP728Suk64llDud/WrShEWl2/OEwZj/fk8qZ/IcFijRwPvAfy/ tyktRp9gKOuwCBSycuyoHCyfWdrz9RsqTNqZHImHSm9FCXRE2YayR/eut3Z6zne8W/AS 06Kzk3YASGCLICMuPyzwpHt09CbK2O2TO4Trall+zHt4oLisgutA6vH367tdybyU0X1y WmboDewRXXGAQrucop1yHplMkSzVCCrLet/NIxFsnRlGCxI+0ScvFCi41PLy+g/h4C8K PaxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=LS5KkYv/TM+vTP0VYCFvkxZPkYL66FuvkRBR7Z6GFqQ=; b=qdi9AuxntJwnfk1G05ESSjnp4oTOd4/o2HUtt7QaAQH8jZ0OOsQ0hUhzbXT7k1j5o7 5Dtoz7n5BK0RL3QZOHojVDZv1FiyUmwak35zY5JQDnxFaCD2BGIQPYzsVvo/MmScyNx0 4Jhfx+jDg6idFxZAGbJa/31tz716P+iwQin5DVN/OiRf60fpxww8uS3E6a7GT8WQGr6s VmtTxRQ312XGdsk9minHaRK75o+jzGI+rqqEBMnQrGKAsXasJZgK+IXfZcrWUrPF0eL3 AAU/YEtBzBap48OTWPCsa+XYKMsfpqajq0erJIQMdmbdYbsMjIfJov38Zl//OTewELUF xXsw== X-Gm-Message-State: AKS2vOyRKaEA7ExT/f+ELoyxESfYs8TpaKMKRm5y7dDLOIizv3/tV3Q8 eas/3tlxJRyEIFDA1U5GY6OBXch3OA3s X-Received: by 10.55.165.17 with SMTP id o17mr38768662qke.14.1499025918769; Sun, 02 Jul 2017 13:05:18 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20170702203252.11c22a94@ntlworld.com> References: <170624120310.ZM30935@torch.brasslantern.com> <20170630143347.7f1c252c@pwslap01u.europe.root.pri> <20170630221610.442726ab@ntlworld.com> <20170702203252.11c22a94@ntlworld.com> From: Bart Schaefer Date: Sun, 2 Jul 2017 13:05:18 -0700 Message-ID: Subject: Re: interrupt handling bug (again?) To: Peter Stephenson Cc: zsh workers Content-Type: text/plain; charset="UTF-8" Thanks for digging into this. I'm not git-enabled at the moment, is 41386 instead of or as well as 41384? Now we just have to deal with (not) disowning those jobs. I suppose we could delay the disown until they are resumed, or something.