From: James Bottomley <jbottomley@parallels.com>
To: "rob@landley.net" <rob@landley.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"plagnioj@jcrosoft.com" <plagnioj@jcrosoft.com>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"gleb@kernel.org" <gleb@kernel.org>,
"broonie@kernel.org" <broonie@kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"jkosina@suse.cz" <jkosina@suse.cz>,
"paulmck@linux.vnet.ibm.com" <paulmck@linux.vnet.ibm.com>,
"henrik@austad.us" <henrik@austad.us>,
"len.brown@intel.com" <len.brown@intel.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"mingo@elte.hu" <mingo@elte.hu>
Subject: Re: [PATCH] Documentation cleanup, update 00-INDEX files in Documentation/
Date: Sun, 2 Feb 2014 18:09:35 +0000 [thread overview]
Message-ID: <1391364575.2178.14.camel@dabdike.int.hansenpartnership.com> (raw)
In-Reply-To: <52EDEE17.4010205@landley.net>
On Sun, 2014-02-02 at 01:04 -0600, Rob Landley wrote:
> Back before kernel.org did its epic barn door locking after the horses
> escaped, I used to use them to generate HTML indexes for
> kernel.org/doc/Documentation, but sometime after they took away my
> ability to rsync updates to that they replaced that directory with a raw
> git checkout. I'm still waiting for them to replace the HTML versions of
> the menuconfig help text and the htmldocs output with raw git checkouts too.
>
> I periodically poke them about it, ala
> https://bugzilla.kernel.org/show_bug.cgi?id=52721#c7 but the answer is
> always crickets chirping or "you should upload web pages with git just
> like you browse the web with git, watch video with git, play skyrim with
> git, edit code with git, compile code with git... there is no other
> software tool." At which point I wander off for another 6 months.
>
> So I used to have a use for it, but since kernel.org got all paranoid I
> can't use it that way anymore. (That's why I haven't been updating these
> files when the patches themselves don't. It's on my todo list, but it's
> really hard to _care_ when they so obviously don't.)
Has it not occurred to you that everyone else moved on from this. Sure
there were annoying and painful adjustments that had to be made and
processes that had to be completely rebuilt and sure it was hard to
build a chain of trust to people in obscure places but everyone else did
it.
Business people are fond of dividing the world into Doers and Whiners.
I don't entirely buy this because in my personal experience if something
ends up being really hard, Doers like to whine about how hard it was to
do in the pub afterwards ... I know I do, particularly over single
malts. The essential truth, I think, is that people with the drive to
do something use that drive to overcome obstacles in their path; people
without it use the obstacles as an excuse for why something didn't get
done. Fundamentally, Open Source is about Doers and thus, while there
are many self help groups for Whiners Open Source lists like LKML aren't
among them.
James
next prev parent reply other threads:[~2014-02-02 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 0:27 Henrik Austad
2014-01-30 2:25 ` Paul E. McKenney
2014-01-30 4:24 ` Rob Landley
2014-01-30 7:33 ` Henrik Austad
2014-01-31 22:24 ` Andrew Morton
2014-02-01 16:50 ` Henrik Austad
2014-02-02 7:04 ` Rob Landley
2014-02-02 18:09 ` James Bottomley [this message]
2014-02-12 2:35 ` Paul Gortmaker
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=1391364575.2178.14.camel@dabdike.int.hansenpartnership.com \
--to=jbottomley@parallels.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=gleb@kernel.org \
--cc=henrik@austad.us \
--cc=hpa@zytor.com \
--cc=jkosina@suse.cz \
--cc=len.brown@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=plagnioj@jcrosoft.com \
--cc=rob@landley.net \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®