From: Dana Lacoste <dana.lacoste@peregrine.com>
To: "'Chris Ricker'" <kaboom@gatech.edu>,
Linus Torvalds <torvalds@transmeta.com>
Cc: World Domination Now! <linux-kernel@vger.kernel.org>
Subject: RE: ANOTHER modest proposal -- We need a documentation package
Date: Wed, 30 Jan 2002 07:03:05 -0800 [thread overview]
Message-ID: <B51F07F0080AD511AC4A0002A52CAB445B2B2B@ottonexc1.ottawa.loran.com> (raw)
> For example,
> no one owns linux/Documentation. As the person nominally in charge of
> linux/Documentation/Changes, there's no one between me and
> you, period, let
> alone anyone between me and you that you trust.... And I
> realize that you
> don't consider documentation very important, but there are
> other segments of
> the Linux source tree for which this breakdown in hierarchy
> is also true....
Here's an idea :
Take linux/Documentation and split it into a separate package.
that way Linus doesn't need to care about documentation, it can
be maintained separately. Having documentation packages co-released
with the kernel, but separately maintained would fix this problem,
would it not?
Dana Lacoste
Ottawa, Canada
next reply other threads:[~2002-01-30 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 15:03 Dana Lacoste [this message]
2002-01-30 15:34 ` Alan Cox
2002-01-30 16:25 ` Jeff Garzik
2002-01-30 15:23 Dana Lacoste
2002-01-30 16:29 ` Jeff Garzik
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=B51F07F0080AD511AC4A0002A52CAB445B2B2B@ottonexc1.ottawa.loran.com \
--to=dana.lacoste@peregrine.com \
--cc=kaboom@gatech.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®