From: Jeremy Bennett <jeremy.bennett@embecosm.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] Openrisc Specification
Date: Tue, 4 Oct 2016 08:20:29 +0100 [thread overview]
Message-ID: <7f167af2-281d-008d-858d-8579818aa94d@embecosm.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1610040755170.3778@lianli.shorne-pla.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/10/16 01:24, Stafford Horne wrote:
> Hi All,
>
> As many problably know opencores was offline for some time over the
> past week. The openrisc specification process currently depends on
> being able to post specifiations on the wiki here:
> http://opencores.org/or1k/Architecture_Specification
>
> Would anyone be apposed to moving the specification process to
> http://openrisc.io? There is already a page for specification
> setup there.
Hi Stafford,
Until this post I had not realized that openrisc.io was set up by
FOSSi. We need the the librecores.org community hub pointing to it. We
also need the reverse pointer on openrisc.io landing page to point
back to FOSSi and librecores.org. A "FOSSi outside" logo or something!
> If we would agree I could do the work to 1. Add old specification
> history to the openrisc.io page 2. Describe the change submission
> process - Create a page change pull requests - Send mail to this
> mailing list for discssion - Periodically discuss the final cut of
> changes - Update the docs and post the changes back to the
> Specification page and download page
>
> All pages for openrisc.io are stored in git on github
> https://github.com/openrisc/openrisc.github.io
>
> Specication documentation (odf) hosted on github
> https://github.com/openrisc/doc
This is all a good idea, and thanks for offering to do it. There is a
more general job to scrape opencores.org as a matter of urgency before
it goes down for good, so we don't lose 15 years of historical record!
Best wishes,
Jeremy
>
> -Stafford _______________________________________________ OpenRISC
> mailing list OpenRISC at lists.librecores.org
> https://lists.librecores.org/listinfo/openrisc
- --
Tel: +44 (1590) 610184
Cell: +44 (7970) 676050
SkypeID: jeremybennett
Twitter: @jeremypbennett
Email: jeremy.bennett at embecosm.com
Web: www.embecosm.com
PGP key: 1024D/BEF58172FB4754E1 2009-03-20
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iGMEARECACMFAlfzWD0cHGplcmVteS5iZW5uZXR0QGVtYmVjb3NtLmNvbQAKCRC+
9YFy+0dU4XOMAJ9ubFTQlMS6dR64JJ3OftEmukKJLwCfeAF2LQVwviYPV7lpvpOK
PxTkmk4=
=KNiZ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2016-10-04 7:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 0:24 [OpenRISC] Openrisc Specification Stafford Horne
2016-10-04 7:20 ` Jeremy Bennett [this message]
2016-10-04 17:36 ` Stefan Wallentowitz
2016-10-04 17:39 ` Stefan Wallentowitz
2016-10-06 17:11 ` Stafford Horne
2016-10-22 8:04 ` Stafford Horne
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=7f167af2-281d-008d-858d-8579818aa94d@embecosm.com \
--to=jeremy.bennett@embecosm.com \
--cc=openrisc@lists.librecores.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 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.