public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Tilman Sauerbeck <tilman@code-monkey•de>
To: git@vger•kernel.org
Subject: Shipping man pages?
Date: Thu, 18 May 2006 09:46:32 +0200	[thread overview]
Message-ID: <20060518074630.GA2994@code-monkey.de> (raw)

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

Hi,
atm, the git release tarballs don't contain man pages. They can be
generated from the asciidoc source files, which makes the build depend
on python and asciidoc.

That's *very* inconvenient; would it be possible to include the man
pages in the release tarball?

Or maybe offer them in a separate tarball?

Thanks,
Tilman

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2006-05-18  7:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-18  7:46 Tilman Sauerbeck [this message]
2006-05-18  8:06 ` Shipping man pages? Junio C Hamano
2006-05-18  9:41   ` Mark Rosenstand
2006-05-18 18:33     ` Junio C Hamano
2006-05-18 18:49       ` Linus Torvalds
2006-05-18 10:57   ` Tilman Sauerbeck
2006-05-18  8:10 ` Fernando J. Pereda

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=20060518074630.GA2994@code-monkey.de \
    --to=tilman@code-monkey$(echo .)de \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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