public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sebastian Pipping <sping@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: [gentoo-catalyst] Migrating man page to asciidoc?
Date: Fri, 24 Jun 2011 02:41:48 +0200	[thread overview]
Message-ID: <4E03DD4C.7050005@gentoo.org> (raw)

Hello!


According to git blame, the man page of catalyst hasn't been touched
since 2005.  I would like to migrate it to Asciidoc to ease up future
maintenance.  I would add a Makefile including  a "dist" target to make
sure we always ship releases with an updated man page.  The list of
supported subarches could be pulled into the man page automatically.

What do you say?

Best,



Sebastian



             reply	other threads:[~2011-06-24  0:42 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-24  0:41 Sebastian Pipping [this message]
2011-06-24  7:07 ` [gentoo-catalyst] Migrating man page to asciidoc? Peter Volkov
2011-06-24 17:16   ` Sebastian Pipping
2011-06-25 17:30     ` Matt Turner
2011-06-25 17:50       ` Sebastian Pipping
2011-06-25 18:31         ` Matt Turner
2011-06-26  2:02         ` Matt Turner
2011-06-26  2:36           ` Sebastian Pipping
2011-06-26  2:49             ` William Hubbs
2011-06-26  3:14               ` Sebastian Pipping
2011-06-26  3:36                 ` William Hubbs
2011-06-26  3:46                   ` William Hubbs
2011-06-26  3:59                     ` Sebastian Pipping
2011-06-26  3:49                   ` Sebastian Pipping
2011-06-26  4:33                     ` William Hubbs
2011-06-26  4:57                       ` Sebastian Pipping
2011-06-26 15:44                         ` Matt Turner
2011-06-26 17:33                           ` William Hubbs
2011-06-26 17:55                             ` Peter Stuge
2011-06-26 18:02                               ` Matt Turner
2011-06-26 18:08                                 ` Peter Stuge
2011-06-26 23:01                                 ` Matt Turner
2011-06-26 23:26                               ` Jorge Manuel B. S. Vicetto
2011-06-27  0:00                                 ` Peter Stuge
2011-06-27  0:31                                   ` Jorge Manuel B. S. Vicetto
2011-06-27  1:06                                     ` Peter Stuge
2011-06-27  1:43                                     ` Sebastian Pipping
2011-06-27  3:58                                       ` Jorge Manuel B. S. Vicetto
2011-06-27 15:55                                         ` Sebastian Pipping
2011-07-03 23:28                                           ` Sebastian Pipping
2011-07-04  0:10                                             ` Matt Turner
2011-07-04  0:18                                               ` Sebastian Pipping
2011-06-27  0:39                                   ` Peter Stuge
2011-06-26 17:55                             ` Matt Turner
2011-06-26 18:17                               ` Sebastian Pipping
2011-06-26 19:25                                 ` William Hubbs
2011-06-26  4:10                 ` Matt Turner
2011-06-26  4:14                   ` Sebastian Pipping
2011-06-26  4:44                     ` William Hubbs
2011-06-26  4:46                       ` Sebastian Pipping
2011-06-27  6:33                   ` Peter Volkov
2011-06-26 16:48           ` Sebastian Pipping
2011-06-26 17:04             ` Peter Stuge

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=4E03DD4C.7050005@gentoo.org \
    --to=sping@gentoo.org \
    --cc=gentoo-catalyst@lists.gentoo.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