From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 85139 invoked by alias); 20 Dec 2019 18:57:05 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 84942 invoked by uid 89); 20 Dec 2019 18:57:04 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 spammy=HX-Languages-Length:1073, H*r:sk:mail-ed, HX-Spam-Relays-External:sk:mail-ed, H*RU:sk:mail-ed X-HELO: us-smtp-delivery-1.mimecast.com Received: from us-smtp-2.mimecast.com (HELO us-smtp-delivery-1.mimecast.com) (207.211.31.81) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 20 Dec 2019 18:57:03 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1576868222; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=LxYnv5wQgmRN/gjiu5xhOB+MWKK5cmc2R/yXCGKlTas=; b=ZYbb8bLhVVSgJiy83+hkyCPXJEw0PtirCPibZ2XxtdELyyg/zeI4oN3iDH4pCkAcb8kRcz K0vu3E2QaOl8pEMestnCrDoEGBVBp5I8xtyHecWVVttDqmeaqvHQXuUNvdW9YOrw+QAQRq DEpcgYvY4W2dQNUaWl891301V9ZkRaE= Received: from mail-ed1-f71.google.com (mail-ed1-f71.google.com [209.85.208.71]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-375-MyL8nawCMeSFHHQjsmdtBw-1; Fri, 20 Dec 2019 13:57:00 -0500 Received: by mail-ed1-f71.google.com with SMTP id b13so6457511edf.0 for ; Fri, 20 Dec 2019 10:57:00 -0800 (PST) Return-Path: Received: from ?IPv6:2001:8a0:f913:f700:56ee:75ff:fe8d:232b? ([2001:8a0:f913:f700:56ee:75ff:fe8d:232b]) by smtp.gmail.com with ESMTPSA id k15sm1180299ejc.35.2019.12.20.10.56.58 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 20 Dec 2019 10:56:58 -0800 (PST) Subject: Re: [PATCH v2 01/24] Preserve selected thread in all-stop w/ background execution To: Tom Tromey References: <20191017225026.30496-1-palves@redhat.com> <20191017225026.30496-2-palves@redhat.com> <87eeyr4tt3.fsf@tromey.com> <87k16q7rr0.fsf@tromey.com> Cc: gdb-patches@sourceware.org From: Pedro Alves Message-ID: <2ffe25e3-24ca-a77c-3712-99bdfe693cdc@redhat.com> Date: Fri, 20 Dec 2019 18:57:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <87k16q7rr0.fsf@tromey.com> X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2019-12/txt/msg00922.txt.bz2 On 12/20/19 6:53 PM, Tom Tromey wrote: >>>>>> "Pedro" == Pedro Alves writes: > > Pedro> On 11/1/19 1:20 PM, Tom Tromey wrote: >>>>>>>> "Pedro" == Pedro Alves writes: >>> > Pedro> + previously selected thread (now exited). We chose the > Pedro> + later, just because that's what GDB used to do. After >>> >>> I think this should say "We choose the latter". > > Pedro> Curious. I actually meant the past as written, since it's a choice > Pedro> that is already made. But I can change it if it reads more naturally > Pedro> to a native speaker. Or I could say "We've chosen". Let me know. > > Can some word be added to make it clear that "later" is intended? > The current text really read as a typo. Oh. Woot. We're talking past each other. I did not notice the "later" vs "latter" typo until now. I thought you were pointing strictly at "chose" vs "choose". The original intention was to say: "We chose the latter" Is that OK? Thanks, Pedro Alves