mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Garzik <garzik@havoc.gtf.org>
To: Dana Lacoste <dana.lacoste@peregrine.com>
Cc: "'Chris Ricker'" <kaboom@gatech.edu>,
	Linus Torvalds <torvalds@transmeta.com>,
	World Domination Now! <linux-kernel@vger.kernel.org>
Subject: Re: ANOTHER modest proposal -- We need a documentation package
Date: Wed, 30 Jan 2002 11:25:44 -0500	[thread overview]
Message-ID: <20020130112544.B21325@havoc.gtf.org> (raw)
In-Reply-To: <B51F07F0080AD511AC4A0002A52CAB445B2B2B@ottonexc1.ottawa.loran.com>
In-Reply-To: <B51F07F0080AD511AC4A0002A52CAB445B2B2B@ottonexc1.ottawa.loran.com>; from dana.lacoste@peregrine.com on Wed, Jan 30, 2002 at 07:03:05AM -0800

On Wed, Jan 30, 2002 at 07:03:05AM -0800, Dana Lacoste wrote:
> 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?

Alas this would simply make it more difficult for me to update things.
For example I update Documentation/networking/8139too.txt each time
there is a corresponding update to drivers/net/8139too.c.  Having to go
from current situation to patching two totally separate trees would be a
PITA and regression from current workflow.

	Jeff




  parent reply	other threads:[~2002-01-30 16:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-30 15:03 Dana Lacoste
2002-01-30 15:34 ` Alan Cox
2002-01-30 16:25 ` Jeff Garzik [this message]
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=20020130112544.B21325@havoc.gtf.org \
    --to=garzik@havoc.gtf.org \
    --cc=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®