public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Chaloupka <jchaloup-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org
Subject: [REVIEW] perftest: new man page
Date: Mon, 25 Aug 2014 08:08:14 +0200	[thread overview]
Message-ID: <53FAD2CE.9020008@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]

Hello,

I am package maintainer responsible for man pages on Fedora and RHEL.
Yesterday, I run into

https://bugzilla.redhat.com/show_bug.cgi?id=948476

stating that binaries of perftest are missing. However, in README, there
is a lot of information (I believe all information needed) for writing
man page for these all binaries. Created man page is attached in the
bugzilla above.


Could you, please, review the man page? It is almost 1:1 copy of
informations from README. If the man page is not meant to exists, I will
state this information into bz. As from COPYING file, content of tarball
is under GPL2 (or BSD) license. I put GPL2+ licence at the top of man
page source code. If the licence is wrong, please, let me know. If you
want your name in Copyright, there is not problem.

If you agree with the page, is there a mailing-list or mail, where bugs
can be sent? I would like to add contact to AUTHORS section. If there
are more authors of perftest, I will add them here too.

Regards
Jan Chaloupka


[-- Attachment #2: ib_atomic_bw.1 --]
[-- Type: application/x-troff-man, Size: 9806 bytes --]

                 reply	other threads:[~2014-08-25  6:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=53FAD2CE.9020008@redhat.com \
    --to=jchaloup-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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