From: daniel.sangorrin@toshiba.co.jp (Daniel Sangorrin)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Wiki for Project X
Date: Wed, 18 Oct 2017 14:39:04 +0700 [thread overview]
Message-ID: <001701d347e4$2cc7bf00$86573d00$@toshiba.co.jp> (raw)
In-Reply-To: 59D64F99.9010909@codethink.co.uk
> -----Original Message-----
> From: Daniel Sangorrin [mailto:daniel.sangorrin at toshiba.co.jp]
> Sent: Wednesday, October 18, 2017 2:38 PM
> To: 'Agustin Benito Bethencourt'
> Cc: 'cip-dev at lists.cip-project.org'
> Subject: RE: Wiki for Project X
>
> Hi,
>
> > -----Original Message-----
> > From: Agustin Benito Bethencourt [mailto:agustin.benito at codethink.co.uk]
> > Sent: Thursday, October 05, 2017 10:28 PM
> > To: Daniel Sangorrin
> > Cc: cip-dev at lists.cip-project.org
> > Subject: Wiki for Project X
> >
> > Hi Daniel,
> >
> > once you want to release Project-X, besides moving the gitlab project
> > away from cip-playground, remember that you need to move the content to
> > the CIP wiki. We are not using the gitlab wiki in order to keep the
> > content in a central place.
> >
> > You can tell gitlab to use an external wiki URL (specific page) in the
> > settings section of your project so the wiki tab, when clicked, will
> > point to the CIP wiki.
> >
> > The current content won't be erased but it won't be reachable unless you
> > disable the external link option back again.
> >
> > Feel free to ask you you have any question about it.
>
> Thanks, I have moved the repository and the wiki page.
> By the way, I upload by mistake one image into the civilinfrastructureplatform:cip-core namespace
> but I didn't know how to delete it.
-upload
+uploaded
>
> Regards,
> Daniel
next prev parent reply other threads:[~2017-10-18 7:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 15:28 [cip-dev] Wiki for Project X Agustin Benito Bethencourt
2017-10-18 7:38 ` Daniel Sangorrin
2017-10-18 7:39 ` Daniel Sangorrin [this message]
2017-10-18 7:50 ` Agustin Benito Bethencourt
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='001701d347e4$2cc7bf00$86573d00$@toshiba.co.jp' \
--to=daniel.sangorrin@toshiba.co.jp \
--cc=cip-dev@lists.cip-project.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