From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 77DDF3858CDB for ; Thu, 23 Mar 2023 14:05:49 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 77DDF3858CDB Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1679580348; 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=w2phFKLknKFs+XExM/iYxk3igDI+13znDRsK9gZCffM=; b=TXNCcDssYl4fSeXHcID59yG+zXSi4h4KGtP3xKYMe8H5jL6UgwgR5ApISS6ucupTz3KXj1 uc0dSTtBCSWVlyaL6/Ifzgz50pfv76RzEPpsCrFkz7ij+jsG9DDgTgz5gu4SLRH/78M0Ms gh8QaBl0MrDFeLAGHRM6NxiA5/qEOwk= Received: from mail-wm1-f70.google.com (mail-wm1-f70.google.com [209.85.128.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-25-TLllaAftMpKU_2J3GCsdNw-1; Thu, 23 Mar 2023 10:05:47 -0400 X-MC-Unique: TLllaAftMpKU_2J3GCsdNw-1 Received: by mail-wm1-f70.google.com with SMTP id bi7-20020a05600c3d8700b003edecc610abso1067678wmb.7 for ; Thu, 23 Mar 2023 07:05:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679580346; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=w2phFKLknKFs+XExM/iYxk3igDI+13znDRsK9gZCffM=; b=f14GgScZiN++bMvGt+4J23rdoZF6DiVY1MWuD2aqlCRsv76Yhj62MDGavMdNV3SyCs a4EcjSryNsuYJqgPJyv02ZoGKyr6jiMPizTQdoCwOeGEyZn8P/HjpsJDrcXt0rDRGB39 gKpDyiwpav9WmafSclZyOHlZWX0Y7cXBFeQKvWD13PSL5B+J+KdnTK+3heiY6+AbCRte MEMry0eTJHgV2a0IhRFjdmQdrsSBSGvtQ84kYxdvbP+8vVxhRoNBvqwpdhccG2Jin7XH jVTm+k7xffsY/gVodkKwa3orAlkDqQo1LOefKJmh563RIbQvgHCWAxT9Hta4/D//pSnX L5PQ== X-Gm-Message-State: AO0yUKXOOKNwGJbPWt1nmXRNLlT/hbObV4SzqTiBmnJ010OzIeCQXnmU wTPJ7IoICXMx1knYVegabydg0eCLfFRvP3ezLmg3QjOlCQF3eIHVx6A0/kbtW+kiabaK5aJfrM3 ls49wFG1Nfhl/XaHrjA== X-Received: by 2002:a7b:ca47:0:b0:3ed:ce6f:e86e with SMTP id m7-20020a7bca47000000b003edce6fe86emr2463834wml.23.1679580346768; Thu, 23 Mar 2023 07:05:46 -0700 (PDT) X-Google-Smtp-Source: AK7set8y5FgjkC4OaVpvjwWpdmzdbPqPLMvoV9rDYrW/VT/OQBBLdGAWalMKJMyygWRc28vAvXhpTw== X-Received: by 2002:a7b:ca47:0:b0:3ed:ce6f:e86e with SMTP id m7-20020a7bca47000000b003edce6fe86emr2463814wml.23.1679580346470; Thu, 23 Mar 2023 07:05:46 -0700 (PDT) Received: from [192.168.1.201] ([139.47.42.170]) by smtp.gmail.com with ESMTPSA id 14-20020a05600c024e00b003ed2384566fsm1983899wmj.21.2023.03.23.07.05.45 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 23 Mar 2023 07:05:46 -0700 (PDT) Message-ID: <1782a2dc-bb85-f4e4-a88c-2b675a1f83bc@redhat.com> Date: Thu, 23 Mar 2023 15:05:45 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0 Subject: Re: [PATCH] ranger: Ranger meets aspell To: Jakub Jelinek , Andrew MacLeod Cc: gcc-patches@gcc.gnu.org References: From: Aldy Hernandez In-Reply-To: X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_BARRACUDACENTRAL,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 3/23/23 14:32, Jakub Jelinek wrote: > Hi! > > I've noticed a comment typo in tree-vrp.cc and decided to quickly > skim aspell -c on the ranger sources (with quick I on everything that > looked ok or roughly ok). > But not being a native English speaker, I could get stuff wrong. > The most questionable seems 3 occurrences of involutary/involutory, > I've used involuntary, but am not sure if that's what you meant. An involutary function is a function who is its own inverse, so AFAIK "involutary" is correct. That being said, it's not a common word, and I must admit I had to look it up when I wrote the comment...mostly to sound smart ;-), so feel free to use another word to avoid confusion. > > Could you please quickly skim it if I'm not making things worse? > Ok for trunk? Otherwise, looks good. Thanks for doing this. Aldy