From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.1 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 10068C433E0 for ; Thu, 14 Jan 2021 00:22:02 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 8303123120 for ; Thu, 14 Jan 2021 00:22:01 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 8303123120 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:49120 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kzqOm-00046y-Eq for qemu-devel@archiver.kernel.org; Wed, 13 Jan 2021 19:22:00 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:40554) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kzqNk-0003ei-Aa for qemu-devel@nongnu.org; Wed, 13 Jan 2021 19:20:56 -0500 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:60365) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.90_1) (envelope-from ) id 1kzqNi-0005uX-1k for qemu-devel@nongnu.org; Wed, 13 Jan 2021 19:20:55 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1610583652; 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=99TF3q84HMnBvXkKX9tWB7QliE3lq2p32PZPn9bogNI=; b=DGywc7rjbzKtD8sZExHFvze0mHPQ712brPzqv0+QJb7lRpd8DHYYCxefL8qrJZ2Z9icmSU kWrFg5oPWTIES0hS4cCW52i+TwwsNRv12L2CVbd23fFXW72S3aI2D93SihNts7lwsMC28F euYOxMk2JjBwW35IAfdS5M4x4tTkK2I= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-386-G7eYyIB8PTmJ0RAryQHeVA-1; Wed, 13 Jan 2021 19:20:51 -0500 X-MC-Unique: G7eYyIB8PTmJ0RAryQHeVA-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 291D415720; Thu, 14 Jan 2021 00:20:50 +0000 (UTC) Received: from [10.10.120.151] (ovpn-120-151.rdu2.redhat.com [10.10.120.151]) by smtp.corp.redhat.com (Postfix) with ESMTP id 2C2EF6062F; Thu, 14 Jan 2021 00:20:43 +0000 (UTC) Subject: Re: [PATCH 1/2] trace: document how to specify multiple --trace patterns To: BALATON Zoltan References: <20210112165859.225534-1-stefanha@redhat.com> <20210112165859.225534-2-stefanha@redhat.com> <542c6083-37ef-8a7c-7b24-f1e4f8dbff3@eik.bme.hu> <20210113094804.GA250553@stefanha-x1.localdomain> <1cd6e449-cdde-adf6-a3ef-b2e95cd04add@redhat.com> <95abf7c3-4338-1659-8c83-e4fb886794b7@eik.bme.hu> From: John Snow Message-ID: <20f2dbbf-638c-4c3f-0513-0c7f1afed15d@redhat.com> Date: Wed, 13 Jan 2021 19:20:42 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: <95abf7c3-4338-1659-8c83-e4fb886794b7@eik.bme.hu> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=jsnow@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Received-SPF: pass client-ip=63.128.21.124; envelope-from=jsnow@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -29 X-Spam_score: -3.0 X-Spam_bar: --- X-Spam_report: (-3.0 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Peter Maydell , Paolo Bonzini , qemu-devel@nongnu.org, Stefan Hajnoczi , Markus Armbruster Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On 1/13/21 6:45 PM, BALATON Zoltan wrote: > > Please don't. That would break all scripts that already call qemu using > single dash options. Forcing everyone to edit their scripts is not nice. > How about also accepting single dash in qemu-img for consistency then > you can use whatever you want in docs as long as single dash still works > for consistency and backward compatibility. That's not what I meant -- I meant for documentation purposes. QEMU can keep accepting single dash, but we should standardize on the spelling for purposes of interactive messages, documentation, etc. --js