linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Nick Kossifidis <mick@ics.forth.gr>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: Nick Kossifidis <mick@ics.forth.gr>, linux-riscv@lists.infradead.org
Subject: Re: Wiki for Linux development
Date: Tue, 01 Jan 2019 21:07:22 +0200	[thread overview]
Message-ID: <28756b6088e9d6d5a2faaf3c16f95255@mailhost.ics.forth.gr> (raw)
In-Reply-To: <4e2b9e9f-d2e2-e5a4-4553-88babc553e18@sifive.com>

Στις 2019-01-01 01:11, Paul Walmsley έγραψε:
> Probably better to have it hosted on kernel.org.
> 
> That way it's handled the same way as almost all of the rest of the
> wiki.kernel.org wikis.
> 
> - Paul
> 

We can't host anything else if we go this way + we can't add any addons 
if we want. I'm ok with moving it if that's what the team wants, since 
docuwiki uses simple files for storage instead of a database, we can 
just copy them over if we want to host it on wiki.kernel.org directly. 
However so far korg helpdesk hasn't replied on the ticket I opened about 
a cname entry, I don't know what's going on, it's been there for months. 
I thought adding a cname should be simpler than hosting another wiki.

Regards,
Nick

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

      parent reply	other threads:[~2019-01-01 19:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-28 15:11 Wiki for Linux development Nick Kossifidis
     [not found] ` <4e2b9e9f-d2e2-e5a4-4553-88babc553e18@sifive.com>
2019-01-01 19:07   ` Nick Kossifidis [this message]

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=28756b6088e9d6d5a2faaf3c16f95255@mailhost.ics.forth.gr \
    --to=mick@ics.forth.gr \
    --cc=linux-riscv@lists.infradead.org \
    --cc=paul.walmsley@sifive.com \
    /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).