All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Jiri Kosina <jkosina@suse.cz>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: update top level 00-INDEX file with new additions
Date: Tue, 19 Feb 2013 11:44:10 -0600	[thread overview]
Message-ID: <1361295850.29465.8@driftwood> (raw)
In-Reply-To: <51224F70.9050806@infradead.org> (from rdunlap@infradead.org on Mon Feb 18 09:57:36 2013)

On 02/18/2013 09:57:36 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...
> 
> comments?

I actually have a script that can audit the 00-INDEX files, as part of  
my kernel.org/doc build stuff:

   http://landley.net/hg/kdocs/file/tip/make

Manually auditing these isn't hard for me, it's just that since  
kernel.org went all-in on locking the barn door after the horses  
escaped, I haven't had access to my old kernel.org account (I need to  
meed kernel developers in person to get keys signed, which doesn't  
happen much).

And even if I did get a new ssh key, you don't get shell access anymore  
you get "kup" which is a git wrapper you can't rsync through. So fixing  
problem 1 opens up problem 2 and I still can't do anything useful.  
(Navigating the new bureaucracy is on my todo list, but not really  
something I sit down and go "oh boy, I should work on THIS" on any  
given evening.)

So I haven't been able to update kernel.org/doc since the breakin, and  
my tools for auditing the 00-INDEX files and htmldocs and menuconfig  
and so on are all tied up with that.

Rob

  parent reply	other threads:[~2013-02-21  1:01 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
2013-02-21 21:31         ` Jiri Kosina
2013-02-23 19:19           ` Rob Landley
2013-02-19 17:44     ` Rob Landley [this message]
  -- 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=1361295850.29465.8@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.