From: Junio C Hamano <junkio@cox.net>
To: Mark Rosenstand <mark@borkware.net>
Cc: git@vger.kernel.org, Tilman Sauerbeck <tilman@code-monkey.de>
Subject: Re: Shipping man pages?
Date: Thu, 18 May 2006 11:33:43 -0700 [thread overview]
Message-ID: <7vodxvkws8.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 1147945298.1320.35.camel@mjollnir
Mark Rosenstand <mark@borkware.net> writes:
> On Thu, 2006-05-18 at 01:06 -0700, Junio C Hamano wrote:
>
>> If you are building from the source, please build from the
>> source. Everything you need is right there.
>
> But asciidoc is a royal PITA to package or install - it doesn't even
> provide a Makefile: http://www.methods.co.nz/asciidoc/userguide.html#X38
>
> Additionally it carries the whole docbook dependency chain with it.
That's a consequence of _your_ choice to build the documentation
files from the source, when I give you preformatted files in
html/man branches and/or prepackaged binary distributions. Even
plain "make all" nor "make install" do not build them.
IOW, not my problem.
We accomplish things by saying "I did this, it solves my
problem, and it would help others -- so I share", not by
demanding others to do things for you by saying "If you do this,
it would solve my problem. Now go do it". That's how open
source works.
>> Why does this have to come up so often, and everybody who asks
>> for them never supplies the patch to do so?
>
> Because it seems like a political decision rather than a technical one
I do not see why that is political. Do you need a politician to
tell you what is source and what isn't?
> (it's trivial to add the docs as a prerequisite for the dist target.)
Being trivial does not change things a whit, because I do not do
things I consider useless only because they are trivial.
You have to first convince me that it is useful to others, and
one way to do so is by showing that you care deeply enough about
it -- doing the work yourself (instead of demanding _me_ to do
something I do not believe is a good idea yet) is a good way to
do so. That would tell me that it is a real problem to you.
When that happens, I might start considering the possibility
that a solution to that problem may be useful to other people.
And it actually makes things actively worse to whine without
doing the work yourself when the necessary change is trivial.
You are saying that you cannot be bothered to do that yourself
even though the change is trivial, which implies you _can_ live
without formatted pages just fine. The conclusion is that not
having the formatted pages is not such a big deal to you (after
all, asciidoc toolchain might be a bear to install, but the
documents formatted in it are very easy to read in the source
form).
Now, with a patch, Tilman showed us he cares deeply enough, so
I'll take a look at it. Thanks, Tilman.
next prev parent reply other threads:[~2006-05-18 18:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 7:46 Shipping man pages? Tilman Sauerbeck
2006-05-18 8:06 ` Junio C Hamano
2006-05-18 9:41 ` Mark Rosenstand
2006-05-18 18:33 ` Junio C Hamano [this message]
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=7vodxvkws8.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=mark@borkware.net \
--cc=tilman@code-monkey.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.