public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dennis Schridde <devurandom@gmx.net>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] Please review: manpage-cleanup
Date: Mon, 24 Sep 2012 00:25:35 +0200	[thread overview]
Message-ID: <1348439140-28207-1-git-send-email-devurandom@gmx.net> (raw)

Hi!

I created a branch for manpage cleanup ([1] and this thread) and would like you to review and possibly merge it.

Note: It is quite cumbersome to review "Reorder and cleanup of ebuild(5)" as a diff. I recommend to just read the DESCRIPTION of the manpage instead. The rest should be more or less unchanged.

Thanks,
Dennis

[1] https://github.com/devurandom/portage/commits/feature/manpage-cleanup



             reply	other threads:[~2012-09-24  0:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-23 22:25 Dennis Schridde [this message]
2012-09-23 22:25 ` [gentoo-portage-dev] [PATCH 1/5] Adjust code of first paragraph of ebuild(5) to 80 char width Dennis Schridde
2012-09-23 22:25 ` [gentoo-portage-dev] [PATCH 2/5] Fix referencens to Dependencies section of ebuild(5) Dennis Schridde
2012-09-23 22:25 ` [gentoo-portage-dev] [PATCH 3/5] Better documentation of PDEPEND in ebuild(5) Dennis Schridde
2012-09-23 22:25 ` [gentoo-portage-dev] [PATCH 4/5] Improve wording of *DEPEND variable description in ebuild(5) a bit Dennis Schridde
2012-09-23 22:25 ` [gentoo-portage-dev] [PATCH 5/5] Reorder description of --root-deps in emerge(1) Dennis Schridde
2012-09-23 22:38 ` [gentoo-portage-dev] Please review: manpage-cleanup Dennis Schridde
2012-09-24  2:46 ` Zac Medico
2012-09-24  9:54   ` Dennis Schridde
  -- strict thread matches above, loose matches on Subject: below --
2012-09-23 22:28 Dennis Schridde
2012-09-23 22:36 ` Dennis Schridde
2012-09-23 22:32 Dennis Schridde

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=1348439140-28207-1-git-send-email-devurandom@gmx.net \
    --to=devurandom@gmx.net \
    --cc=gentoo-portage-dev@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