From: "J.H." <warthog19@eaglescrag•net>
To: Junio C Hamano <gitster@pobox•com>
Cc: Sverre Rabbelier <srabbelier@gmail•com>,
Matthieu Moy <Matthieu.Moy@grenoble-inp•fr>,
Petr Baudis <pasky@suse•cz>,
git@vger•kernel.org
Subject: Re: [RFC] Git Wiki Move
Date: Fri, 15 Jan 2010 16:05:26 -0800 [thread overview]
Message-ID: <4B5102C6.3020709@eaglescrag.net> (raw)
In-Reply-To: <7vska7rkr0.fsf@alter.siamese.dyndns.org>
On 01/15/2010 03:50 PM, Junio C Hamano wrote:
> Sverre Rabbelier <srabbelier@gmail•com> writes:
>
>> On Sat, Jan 16, 2010 at 00:18, J.H. <warthog19@eaglescrag•net> wrote:
>>> Quick update - I think I've got the vast majority of the obvious and
>>> simple to correct problems fixed at http://git.wiki.kernel.org anyone
>>> want to run through and see if there's anything else that would be
>>> considered a show stopper?
>>
>> I'd say it's pretty embarassing if our FAQ [0] is broken.
>
> Many "<<GitLink(foobar}}" in the FAQ page do seem like result of
> mechanical misconversion.
>
> John, thanks for doing this. If people fix things up manually, can they
> expect their fixes will be kept from now on, iow, the changes will not be
> overwritten by "Ok, I found a much better mechanical conversion tool and
> updated with the latest snapshot from the original wiki" in the future?
I have no intention of re-converting the data, so yes fixups will not be
squashed. I've got a small bot script right now that if there's a
change that needs to happen pretty universally across the entirety wiki
it can be run (it's written in perl, reads in the page text, runs the
conversion and re-uploads it), so if there's something that's
particularly repetitive people can get me some code that would fix the
problem.
So again short answer: I'm at the point where I'd rather clean-up what
we've got then try and re-import the data.
- John 'Warthog9' Hawley
next prev parent reply other threads:[~2010-01-16 0:06 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.
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. [this message]
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=4B5102C6.3020709@eaglescrag.net \
--to=warthog19@eaglescrag$(echo .)net \
--cc=Matthieu.Moy@grenoble-inp$(echo .)fr \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=pasky@suse$(echo .)cz \
--cc=srabbelier@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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