From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS53758 23.128.96.0/24 X-Spam-Status: No, score=-4.4 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A, RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by dcvr.yhbt.net (Postfix) with ESMTP id 6B0E31F8C6 for ; Sun, 11 Jul 2021 10:24:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232141AbhGKK1B (ORCPT ); Sun, 11 Jul 2021 06:27:01 -0400 Received: from smtprelay04.ispgateway.de ([80.67.31.32]:49016 "EHLO smtprelay04.ispgateway.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232106AbhGKK1B (ORCPT ); Sun, 11 Jul 2021 06:27:01 -0400 Received: from [87.152.144.190] (helo=[192.168.2.202]) by smtprelay04.ispgateway.de with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1m2Wby-0001dp-0D; Sun, 11 Jul 2021 12:22:58 +0200 Subject: Re: PATCH: improve git switch documentation To: Sergey Organov Cc: Felipe Contreras , Junio C Hamano , git@vger.kernel.org References: <877di13hhe.fsf@osv.gnss.ru> <60e67389a4adc_306ac1208fd@natae.notmuch> <4057b3ac-a77c-0d5f-d3f4-ad781754aae4@mfriebe.de> <60e736e72da68_30939020850@natae.notmuch> <155308af-42ad-b044-fb37-676251a9b7e1@mfriebe.de> <60e762243aab1_30a7b02089@natae.notmuch> <2b85a7eb-d0be-65e7-ecbb-1750abf53e53@mfriebe.de> <60e79c31aaa72_30b8a4208c1@natae.notmuch> <65362688-b65b-661c-20c1-94d7dc2118c7@mfriebe.de> <60e874e1c6845_215320861@natae.notmuch> <60e88a4b8592f_16bcb2082b@natae.notmuch> <60e9f8d462bd9_7ef20898@natae.notmuch> <6f43b36b-abe1-41f2-6138-e820c974b1bd@mfriebe.de> <60ea07e3495e8_7ef2081d@natae.notmuch> <30e4c874-6b87-b03d-fa33-fde5b7e50b2a@mfriebe.de> <878s2dgu4d.fsf@osv.gnss.ru> <0d7190ae-e64e-d1fa-2367-29f302c2ff7e@mfriebe.de> <87sg0lfayd.fsf@osv.gnss.ru> From: Martin Message-ID: <4cb46126-c816-065f-9052-8ef392c7778b@mfriebe.de> Date: Sun, 11 Jul 2021 12:24:10 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: <87sg0lfayd.fsf@osv.gnss.ru> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Df-Sender: bWVAbWZyaWViZS5kZQ== Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On 11/07/2021 11:37, Sergey Organov wrote: > Martin writes: > I did suggest a wording in that post: > > "Allows to reuse . Commits from the former branch may > become unreferenced." > > Another one could be: > > "Allows to reuse . Commits from the former branch could be > lost." > "lost" is perfect for me. "could be" is a good replacement for "may". It much stronger points to "this may or may not be" "could be" should definitely be used. Afaik many tech docs try to avoid "may", "can", "must not"....