From: David Woodhouse <dwmw2@infradead.org>
To: Josh Boyer <jdub@us.ibm.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS3 document
Date: Thu, 27 Jan 2005 09:47:31 +0000 [thread overview]
Message-ID: <1106819251.783.141.camel@baythorne.infradead.org> (raw)
In-Reply-To: <1106775037.6955.50.camel@weaponx.rchland.ibm.com>
On Wed, 2005-01-26 at 15:30 -0600, Josh Boyer wrote:
> > Instead of editing this file via CVS, would it be possible (and a
> > good idea) to use a wiki? That would make it really easy (and time
> > efficient) for anyone to modify it.
> >
> That was brought up on IRC and vetoed. Wikis tend to get spammed with
> useless or out-dated information, and it's another application for the
> server to have to keep up are the reasons I believe.
It wasn't really vetoed. I just said that _I_ didn't want to run a Wiki,
for much those reasons. I also pointed out that having a minor barrier
to entry wasn't _necessarily_ a bad thing. Hell, most days even I
shouldn't be permitted to commit to it. Why should we open it to the
world? :)
Send patches if you want to make changes. If you make a habit of sending
patches we actually want to apply, we'll give you an account and you can
do it yourself. That's the way it's always worked for the code, and it
doesn't seem to have been much of a problem.
--
dwmw2
next prev parent reply other threads:[~2005-01-27 9:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 10:11 JFFS3 document Artem B. Bityuckiy
2005-01-26 20:51 ` Michael
2005-01-26 21:30 ` Josh Boyer
2005-01-27 9:47 ` David Woodhouse [this message]
2005-01-27 13:17 ` Jörn Engel
2005-01-27 16:10 ` JFFS3 document / wiki [OT] Cam
2005-01-27 16:38 ` Jörn Engel
2005-01-27 16:37 ` jasmine
2005-01-27 16:51 ` Jörn Engel
2005-01-27 17:35 ` Jörn Engel
2005-01-27 18:27 ` Cam
2005-01-27 19:01 ` Jörn Engel
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=1106819251.783.141.camel@baythorne.infradead.org \
--to=dwmw2@infradead.org \
--cc=jdub@us.ibm.com \
--cc=linux-mtd@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox