All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Jiri Kosina <jkosina@suse.cz>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: update top level 00-INDEX file with new additions
Date: Wed, 20 Feb 2013 23:32:31 -0600	[thread overview]
Message-ID: <1361424751.29465.11@driftwood> (raw)
In-Reply-To: <512391DA.6090706@windriver.com> (from paul.gortmaker@windriver.com on Tue Feb 19 08:53:14 2013)

On 02/19/2013 08:53:14 AM, Paul Gortmaker wrote:
> On 13-02-18 10:57 AM, Randy Dunlap wrote:
> > On 02/18/13 01:39, Jiri Kosina wrote:
> >> On Thu, 14 Feb 2013, Paul Gortmaker wrote:
> >>
> >>> It seems there are about 80 new, but undocumented addtions at
> >>> the top level Documentation directory.  This fixes up the top
> >>> level 00-INDEX by adding new entries and deleting a couple  
> orphans.
> >>> Some subdirs could probably still use a check/cleanup too though.
> >
> > After this patch, I would prefer to see a requirement that each  
> Documentation/
> > file contain a "topic" line and then generate INDEX files from  
> those automatically...

1) Have you tried running make htmldocs recently? Notice how much  
cleanup needs to be done there? (Yes, it's on my todo list.)

2) How many people know that make htmldocs exists? The advantage of  
00-INDEX is you don't need to be that familiar with the kernel  
documentation to notice it _exists_. If you have to run a step to  
generate it, half the point goes away.

> >
> > comments?
> 
> Rules can sometimes be so inflexible as to prevent additions.
> I think I'd rather see a makefile target that does some sanity
> checks, so that kernel janitors and the like are more apt to
> send trivial patches before it falls behind by 80+ entries like
> it was just recently.   Just my $0.02 opinion.
> 
> P.

Ran my doclinkcheck.py against the "lying around" snapshot I have (less  
than a week old). The attached file is the output. I need to add  
filters. (I should break down and add an X: rule for  
Documentation/devicetree because that's maintained separately by domain  
experts and is a huge source of churn rending the linux-doc list nearly  
unusable. And burying my personal mailbox a bit.)

Also, this doesn't catch stuff like:

cd Documentation; for i in $(find zh_CN -type f); do X="$(echo $i | sed  
's@^zh_CN/@@')"; find $X -newer $i; done

(I.E. are any translated files older than the file that got  
translated...)

Today, Greg KH signed my pgp key at CELF, meaning I can start the  
process of getting my kernel.org account back, which gets me unblocked  
on a lot of this. (I always have the todo list of doom, but all I've  
been able to do since the breakin is forward patches to -trivial, and  
sending big stuff through that seems inappropriate somehow...)

Rob

  reply	other threads:[~2013-02-21 18:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-14 20:20 [PATCH] Documentation: update top level 00-INDEX file with new additions Paul Gortmaker
2013-02-18  9:39 ` Jiri Kosina
2013-02-18 15:57   ` Randy Dunlap
2013-02-19 14:53     ` Paul Gortmaker
2013-02-21  5:32       ` Rob Landley [this message]
2013-02-21 21:31         ` Jiri Kosina
2013-02-23 19:19           ` Rob Landley
2013-02-19 17:44     ` Rob Landley
  -- strict thread matches above, loose matches on Subject: below --
2013-01-29 15:34 Paul Gortmaker
2013-02-07  5:28 ` Rob Landley

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=1361424751.29465.11@driftwood \
    --to=rob@landley.net \
    --cc=jkosina@suse.cz \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=rdunlap@infradead.org \
    /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.