Received: by 2002:a05:6a10:a852:0:0:0:0 with SMTP id d18csp856116pxy; Fri, 30 Apr 2021 19:07:16 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyXs3xwRgnG7it2+mdHO/+WmNe0CNMrR7NBB8XbE+2Qhj18BHS/8HmF6oYj22HrwinzNuhv X-Received: by 2002:a05:6402:1255:: with SMTP id l21mr9117844edw.362.1619834836695; Fri, 30 Apr 2021 19:07:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1619834836; cv=none; d=google.com; s=arc-20160816; b=rMH8cNs4VvI255Kg2y4zoUVQpHFhj62fA+oLjP4Pq7LMwjfWPTQx3YcTc+ZK10dTpT 5FKUQ5naW+dZhX5RbPGN7YwcMALkEjPwmALMnR+7Zbje+r2R96lTsT8je37i7DAdiib4 3bg7DY6f7knz/bMXTFdpHebaauuODxTbF83X1t7SA0ynJJY7oWVcqPECk9pgy0tvSm7V D53/5YVBJoH8mPDLlTfwalYmtkqFKuDREFj2j4hwKmeeApGZaXve7pJSzczC171l6hyS fyzhYR0VOy5dXlfek5PhrjvzTUdlXBsI45wjBq7hEXpzzmQ5BBoPv256HbNePsmZvxjK a48Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:to:references:message-id :content-transfer-encoding:cc:date:in-reply-to:from:subject :mime-version; bh=ILEKRuXMi7yXk6EVQnnA4Aivp3pTcdIPVWN9FvfRcVc=; b=SedkfQCuFWOth/ZxCtVrOwP27b+M08I1eN73SoCQ26NvoMUMM0+zyyOA4AT0B9BDMX YTkAnXjTLBRnt5/a4lqKab11978vsMqcY0aX9+QFD3jpNmfmkYUJapephbqYk0/VoZSP e2viQjTeJm/g+dm/kK0zIzFaZm98LzzO+gCiOtPn+WqTNYGbEBoleNdxuGFQ7qd9lOd4 j2KzlS7eLzTRuNKaMIIOqMhySorzq7pxdYasEKPXXlNHbdt1AeqNmK+eEcRIaruCve8T MUmrkbZ68VJ89vkKFmhjEOtuCmAiajWfBmZYXih/Sh/69F5714/8ZYbE/wTfFknFdXkM 0xcw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id h1si3472815ede.545.2021.04.30.19.06.39; Fri, 30 Apr 2021 19:07:16 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231439AbhEACAb convert rfc822-to-8bit (ORCPT + 99 others); Fri, 30 Apr 2021 22:00:31 -0400 Received: from coyote.holtmann.net ([212.227.132.17]:46864 "EHLO mail.holtmann.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231435AbhEACAa (ORCPT ); Fri, 30 Apr 2021 22:00:30 -0400 Received: from smtpclient.apple (p4fefc624.dip0.t-ipconnect.de [79.239.198.36]) by mail.holtmann.org (Postfix) with ESMTPSA id 05F80CED0F; Sat, 1 May 2021 04:07:30 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.80.0.2.43\)) Subject: Re: [BlueZ v2] monitor: Update manpage From: Marcel Holtmann In-Reply-To: Date: Sat, 1 May 2021 03:59:40 +0200 Cc: Tedd Ho-Jeong An , "linux-bluetooth@vger.kernel.org" Content-Transfer-Encoding: 8BIT Message-Id: References: <20210428062214.335567-1-hj.tedd.an@gmail.com> <87c5b74558d3062f301dbfa28b93cdbfbe310dd2.camel@gmail.com> To: Luiz Augusto von Dentz X-Mailer: Apple Mail (2.3654.80.0.2.43) Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org Hi Luiz, >>>> From: Tedd Ho-Jeong An >>>> >>>> This patch updates the manpage for btmon written in rst format. >>>> --- >>>> Makefile.am | 26 ++++--- >>>> Makefile.tools | 4 ++ >>>> configure.ac | 4 ++ >>>> doc/btmon.txt | 35 ---------- >>>> monitor/btmon.rst | 172 ++++++++++++++++++++++++++++++++++++++++++++++ >>> >>> I do wonder why you change the location from doc to monitor, I think >>> we actually should keep all the documentation under doc and perhaps >>> even have a dedicated make target for those since we would likely want >>> to generate all the manpages from rst which may be time consuming so >>> people not interested on it can just skip it. >> >> I converted all manpages in the tree to .rst and ready to submit. >> Can I combine all in this series or wait for this to merge first? > > Have you added a make target for those? I really don't mind having the > manpages generated within the same location of the binary, although I > think it would be more organized to have it in one place, but a make > target would probably be a good practice. the way how this works is that in a git tree they are always generated unless disabled or rst2man is not available. And in a tarball, the generated manual pages are shipped, which means they are not needed to be generated. So no specific make target required. Lets just copy what iwd repository doing since that is working fine. Regards Marcel