public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Andreas Mohr <andi@lisas.de>
Cc: Andreas Mohr <andi@lisas.de>, Kris Rusocki <kszysiu@braxis.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: cover CONFIG_BINFMT_SCRIPT in init.txt
Date: Thu, 06 Jun 2013 20:33:20 -0500	[thread overview]
Message-ID: <1370568800.2776.75@driftwood> (raw)
In-Reply-To: <20130603202656.GA1102@rhlx01.hs-esslingen.de> (from andi@lisas.de on Mon Jun  3 15:26:56 2013)

On 06/03/2013 03:26:56 PM, Andreas Mohr wrote:
> Hi,
> 
> On Mon, Jun 03, 2013 at 06:16:12AM -0500, Rob Landley wrote:
> > On 05/30/2013 03:33:10 PM, Andreas Mohr wrote:
> > >It's somewhat sad to see that that file remained at only one
> > >initial commit
> > >since 2010, thus thumbs up for your help!
> > >
> > >Docs in general seem to be a wee bit too unmaintained.
> >
> > Are you volunteering?
> 
> Yeah (sort of ;) - in fact I keep piling up some doc updates locally
> and am just waiting for them to reach critical mass
> (but first I need to get some certain driver updates submitted  
> anyway).
> 
> Andreas Mohr

No one person is an expert in every file in Documentation. My big todo  
items are centered around librarian work: reorganizing the layout of  
the directory so it's not a giant heap with everybody in the world  
dumping stuff into the root directory, or weird little crevices like  
pti/ and pps/ that have their own directory with one file in it.

Unfortunately, Documentation is the greatest source of bikeshedding in  
the kernel. Even as the directory's nominal maintainer, I can't say  
"translations don't belong in there, they belong on the web" because  
Greg KH thinks they do so he'll check them in anyway. And then nobody  
maintains them because anybody who can read the english versions (and  
thus update the translations) doesn't need the translations.

There's functional stuff in there like the devicetree bindings. There's  
a Makefile that compiles stuff under Documentation, and not just the  
htmldocs but actual code. I still don't really know why...

Unfortunately, I only really get time to deal with this sort of thing  
in the downtime between contracts, and last time I had a gap the  
massive barn-door-locking after the kernel.org breakin still had my  
account disabled because I hadn't been to an in-person conference to  
get a new pgp key signed in years. (And now that I've been to a  
conference and gotten one signed, I need to sit down and write a new  
rsync replacement on top of kup because non-security people wrote a  
bespoke security wrapper for kernel.org to replace shell access, which  
means my old rsync script that updated http://kernel.org/doc needs to  
be replaced with a rube goldberg monstrosity to do the same thing in a  
much more complicated and less efficient way.)

It's on the todo list. (You may have noticed I'm a couple days behind  
on just email. Next scheduled gap's in August...)

Rob

  reply	other threads:[~2013-06-07  1:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30 19:24 [PATCH] Documentation: cover CONFIG_BINFMT_SCRIPT in init.txt Kris Rusocki
2013-05-30 20:33 ` Andreas Mohr
2013-06-03 11:16   ` Rob Landley
2013-06-03 20:26     ` Andreas Mohr
2013-06-07  1:33       ` Rob Landley [this message]
2013-06-08  9:13         ` Andreas Mohr

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=1370568800.2776.75@driftwood \
    --to=rob@landley.net \
    --cc=andi@lisas.de \
    --cc=kszysiu@braxis.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox