public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: artusemrys@sbcglobal.net, marc@osknowledge.org, greg@kroah.com,
	linux-kernel@vger.kernel.org, rdunlap@xenotime.net,
	xose.vazquez@gmail.com
Subject: Re: [RFC] Documentation dir is a mess
Date: Tue, 22 Nov 2005 10:42:23 -0800	[thread overview]
Message-ID: <20051122104223.00aa9420.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0511220839020.12166@gandalf.stny.rr.com>

Steve wrote:
> This would need to be done in a step by step basis.

True.  Good points.  If this directory reorg is part of a larger effort
to improve the Doc subtree, and someone is intending to put in that
effort and will do a good job, then more power to them.

If it's just a one time rearrangement of the existing docs, then it
would likely be more nuisance than value.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

  reply	other threads:[~2005-11-22 18:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-20 12:19 [RFC] Documentation dir is a mess Xose Vazquez Perez
2005-11-21  0:30 ` Greg KH
2005-11-21  1:56   ` Steven Rostedt
2005-11-21 17:34     ` Marc Koschewski
2005-11-22  6:06       ` Matthew Frost
2005-11-22  9:18         ` Paul Jackson
2005-11-22 13:46           ` Steven Rostedt
2005-11-22 18:42             ` Paul Jackson [this message]
2005-11-22  9:56         ` Marc Koschewski
2005-11-25 19:53   ` [RFC PATCH] was " Xose Vazquez Perez
2005-11-21 16:28 ` Rob Landley
2005-11-21 16:44   ` Christopher Friesen
2005-11-21 18:05     ` Rob Landley
2005-11-21 19:22       ` Christopher Friesen
2005-11-21 16:46   ` Jiri Slaby
2005-11-25 20:27   ` Xose Vazquez Perez

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=20051122104223.00aa9420.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=artusemrys@sbcglobal.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc@osknowledge.org \
    --cc=rdunlap@xenotime.net \
    --cc=rostedt@goodmis.org \
    --cc=xose.vazquez@gmail.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