From: Jason Gunthorpe <jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: "Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH rdma-core] Support writing man pages in MarkDown
Date: Tue, 12 Dec 2017 16:27:21 -0700 [thread overview]
Message-ID: <20171212232721.GN16588@mellanox.com> (raw)
In-Reply-To: <1828884A29C6694DAF28B7E6B8A82373AB1C234C-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Tue, Dec 12, 2017 at 11:11:15PM +0000, Hefty, Sean wrote:
> > Since this may be a problem, I am thinking about following the
> > libfabric approach and either including the precompiled man pages in
> > the source tree, or just providing a framework for downstream to add-
> > on precompiled files (with a cbuild command to make them) Looking for
> > feedback on what path is best..
>
> FWIW, one of the reasons libfabric went with pre-compiled man pages
> was to include a date for the last edit. A service automatically
> updates the date when updating the page.
This isn't going to be so useful here since all the markdown pages
were created today..
What I did was to copy the date from the original man page over to the
markdown header:
date: 2015-01-29
So the date visible in the man page doesn't change from what it was
before (which in turn is a kind of meaningless value these days since
we never bothered to keep it up to date in most cases)
Other projects don't bother with the date, for instance systemd just
drops in in the package version number in that space, which actually
seems more usefull to me.
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-12-12 23:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 22:59 [PATCH rdma-core] Support writing man pages in MarkDown Jason Gunthorpe
[not found] ` <20171212225936.GA29558-uk2M96/98Pc@public.gmane.org>
2017-12-12 23:11 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A82373AB1C234C-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2017-12-12 23:27 ` Jason Gunthorpe [this message]
2017-12-24 12:03 ` Yishai Hadas
[not found] ` <455f0faf-516b-fa8d-c0d2-d2cee9194e5b-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2017-12-27 9:53 ` Benjamin Drung
[not found] ` <1514368433.4412.2.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-12-27 11:13 ` Leon Romanovsky
[not found] ` <20171227111348.GB3494-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-12-27 11:27 ` Benjamin Drung
[not found] ` <1514374021.4412.9.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-12-27 12:20 ` Leon Romanovsky
[not found] ` <20171227122056.GD3494-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-12-27 13:56 ` Benjamin Drung
2017-12-27 17:44 ` Jason Gunthorpe
[not found] ` <20171227174444.GC31310-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-12-27 18:06 ` Benjamin Drung
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=20171212232721.GN16588@mellanox.com \
--to=jgg-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox