All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J.H." <warthog19@eaglescrag.net>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Petr Baudis <pasky@suse.cz>, git@vger.kernel.org
Subject: Re: [RFC] Git Wiki Move
Date: Thu, 14 Jan 2010 10:56:40 -0800	[thread overview]
Message-ID: <4B4F68E8.5050809@eaglescrag.net> (raw)
In-Reply-To: <vpqbpgxrn32.fsf@bauges.imag.fr>

On 01/14/2010 02:35 AM, Matthieu Moy wrote:
> "J.H." <warthog19@eaglescrag.net> writes:
> 
>> Just a heads up I've got an initial import of the current wiki up at
>> http://git.wiki.kernel.org - some of it was quite a clean conversion,
>> some of it not so much.  Please note that user accounts were not carried
>> over but edit histories were.  I'll work on cleaning up the rest of if
>> tomorrow, assuming that there isn't any objections to Petr's e-mail
>> above.
> 
> My only objection would be "Oh, migrating to another wiki engine will
> be much conversion work", but if you're willing to do it ;-).

It unfortunately goes with the territory, though I'll admit the Moinmoin
-> Mediawiki was the first conversion I've seen where even Mediawiki said:

	There are a number of hacky scripts for this. They are all
	defective in various ways - anyone who does this job does it
	precisely once, so there's no-one who really maintains a good
	converter script.

> This page seems to be an interesting test-case:
> http://git.wiki.kernel.org/index.php/GitFaq
> full of miss-imported formatting, links, ...

That's not actually the worst,

http://git.wiki.kernel.org/index.php/GitRelatedLogos

even after I've cleaned up a chunk of it is still pretty bad.

- John 'Warthog9' Hawley

  reply	other threads:[~2010-01-14 18:56 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-13 23:29 [ANNOUNCE] Git wiki & repo.or.cz migration, donations and volunteers pledge Petr Baudis
2010-01-14  1:24 ` [RFC] Git Wiki Move Petr Baudis
2010-01-14 10:28   ` J.H.
2010-01-14 10:35     ` Matthieu Moy
2010-01-14 18:56       ` J.H. [this message]
2010-01-15 23:18         ` J.H.
2010-01-15 23:21           ` Sverre Rabbelier
2010-01-15 23:50             ` Junio C Hamano
2010-01-16  0:05               ` J.H.
2010-01-16  0:02             ` J.H.
2010-01-16  0:08               ` Sverre Rabbelier
2010-01-16  0:12                 ` Junio C Hamano
2010-01-16  0:28                 ` J.H.
2010-01-16  0:44                   ` Sverre Rabbelier
2010-01-16  1:18                     ` J.H.
2010-01-16 10:17                       ` Clemens Buchacher
2010-01-17 12:00           ` Matthieu Moy
2010-01-17 23:06             ` Johannes Schindelin
2010-01-18  0:43               ` J.H.
2010-01-18  9:53                 ` Johannes Schindelin
2010-01-18 12:03                   ` Johannes Schindelin
2010-01-18 18:47                     ` J.H.
2010-01-18 20:46                       ` Johannes Schindelin
2010-01-21 21:35                       ` Petr Baudis
2010-01-22  0:21                         ` Jakub Narebski
2010-01-22  0:31                           ` Petr Baudis
2010-01-22  0:39                           ` Johannes Schindelin
2010-01-14 10:43     ` Johannes Schindelin
2010-01-14 11:01       ` Johannes Schindelin
2010-01-14 18:52       ` J.H.
2010-01-14 10:48     ` Petr Baudis
2010-01-14 11:03       ` Johannes Schindelin
2010-02-12 11:38     ` Petr Baudis
2010-01-14 10:48   ` Wincent Colaiuta
2010-01-15 17:17   ` Joey Hess
2010-01-15 19:16     ` Johannes Schindelin

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=4B4F68E8.5050809@eaglescrag.net \
    --to=warthog19@eaglescrag.net \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=pasky@suse.cz \
    /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.