From: James Andrewartha <jamesa@daa.com.au>
To: Jeff Garzik <jeff@garzik.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Tejun Heo <htejun@gmail.com>, Albert Lee <albertcc@tw.ibm.com>
Subject: Re: linux-ata.org contributions
Date: Mon, 12 Nov 2007 00:41:52 +0900 [thread overview]
Message-ID: <1194795712.2865.2.camel@zarvora> (raw)
In-Reply-To: <4736395D.1080102@garzik.org>
On Sat, 2007-11-10 at 18:06 -0500, Jeff Garzik wrote:
> Alan Cox wrote:
> > On Sat, 10 Nov 2007 17:11:39 -0500
> > Jeff Garzik <jeff@garzik.org> wrote:
> >
> >> Jeff Garzik wrote:
> >>> Whenever you want to update or add a page, just send a 'git pull'
> >>> request to me...
> >>
> >> Or patches, if you wish to avoid git.
> >
> > Bad idea IMHO
> >
> > You ask Jeff to pull some updates, they go wrong, the website looks a
> > mess, Jeff goes to the pub.
> >
> > There's an immediacy about the display of web content that often benefits
> > from an immediacy of updates/fixing. The web just isn't batch processed.
>
> I wouldn't push it out unless it looked OK in my browser.
>
> But overall I tend to dislike wikis. They enable collaboration, but
> tend to be uniformly ugly, cumbersome, and CPU intensive.
What about ikiwiki? It's a wiki backed by an RCS, which can be git.
http://ikiwiki.info/ and http://ikiwiki.info/rcs/git/
James Andrewartha
next prev parent reply other threads:[~2007-11-11 15:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-10 22:10 linux-ata.org contributions Jeff Garzik
2007-11-10 22:11 ` Jeff Garzik
2007-11-10 23:03 ` Alan Cox
2007-11-10 23:06 ` Jeff Garzik
2007-11-10 23:10 ` Alan Cox
2007-11-11 15:41 ` James Andrewartha [this message]
2007-11-12 1:18 ` Tejun Heo
2007-11-12 1:57 ` Jeff Garzik
2007-11-12 2:01 ` Tejun Heo
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=1194795712.2865.2.camel@zarvora \
--to=jamesa@daa.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertcc@tw.ibm.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).