Linux-Trace-Devel Archive on lore.kernel.org
 help / color / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Zamir SUN <sztsian@gmail.com>
Cc: linux-trace-devel@vger.kernel.org,
	Tzvetomir Stoyanov <tstoyanov@vmware.com>
Subject: Re: libtraceevent: make doc-install tries different file names than generated
Date: Mon, 12 Oct 2020 13:58:04 -0400
Message-ID: <20201012135804.2489f70e@gandalf.local.home> (raw)
In-Reply-To: <b592e388-5af1-5269-37ce-8ca9e91c84dd@gmail.com>

On Mon, 12 Oct 2020 20:35:20 +0800
Zamir SUN <sztsian@gmail.com> wrote:

> Hi Steve,
> 
> I just tried compiling the document. IIUC with this patch, the man pages 
> are generated. Most of them still have tep_ prefix. Not sure if this is 
> intended so I'm posting the list of generated man page in gist as it's a 
> bit long.
> https://gist.github.com/sztsian/442db46a48c1d1ec3500b161a1232a0a
> 
> OTOH, I notice that a lot of generation tasks was executing during the 
> doc-install phase. I'm really not familiar with man page compiling, so 
> can you check if this is an intended way? I posted the doc-install log 
> in the following link.
> 
> https://gist.github.com/sztsian/6d1588272c07c7b2c3bed14a049b7df2
> 

Bah, I'm not sure how the documentation build system here works. Ideally,
we want to make sure that "man tep_.." works, and people don't need to
state "man libtraceevent_...", as the tep_* commands are what will be used.

Let me investigate this.

Thanks!

-- Steve

      reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-08  9:50 Zamir SUN
2020-10-09 14:49 ` Steven Rostedt
2020-10-12 12:35   ` Zamir SUN
2020-10-12 17:58     ` Steven Rostedt [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201012135804.2489f70e@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=sztsian@gmail.com \
    --cc=tstoyanov@vmware.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-Trace-Devel Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-trace-devel/0 linux-trace-devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-trace-devel linux-trace-devel/ https://lore.kernel.org/linux-trace-devel \
		linux-trace-devel@vger.kernel.org
	public-inbox-index linux-trace-devel

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-trace-devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git