public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: overseers@sourceware.org
Subject: Re: setting up sim project web space
Date: Wed, 17 Nov 2021 19:50:38 -0500	[thread overview]
Message-ID: <YZWjXmevwgS+xbjx@vapier> (raw)
In-Reply-To: <YTtKLh3Heuv1gjNn@elastic.org>

[-- Attachment #1: Type: text/plain, Size: 532 bytes --]

On 10 Sep 2021 08:06, Frank Ch. Eigler wrote:
> > i'd like to start a sim landing page for the sim project at
> > https://sourceware.org/sim/
> 
> May I ask why?  Is there talk of separating it from gdb or something?

the sim code has always been buildable & usable independent of gdb.  there
are no requirements in the sim code on gdb.  it can be built & released
independent too.  there are no plans currently to do independent releases,
but there is need for hosting of sim-specific documentation (e.g. manual).
-mike

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-11-18  0:50 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-10  4:17 Mike Frysinger
2021-09-10 12:06 ` Frank Ch. Eigler
2021-11-18  0:50   ` Mike Frysinger [this message]
2021-11-18  0:56     ` Frank Ch. Eigler
2021-11-18  1:38       ` Mike Frysinger
2021-11-18 15:03         ` Mark Wielaard
2021-11-19  8:31           ` Mike Frysinger
2021-11-19  8:42             ` Mike Frysinger
2021-11-19 10:08               ` Mark Wielaard
2021-11-19 11:15                 ` Mike Frysinger
2021-11-19 15:49                   ` Pedro Alves
2021-11-21 13:59                     ` Joel Brobecker
2021-11-24 10:02                       ` Mark Wielaard
2021-11-24 11:16                         ` Mike Frysinger
2022-10-24 16:19                           ` Mike Frysinger
2022-10-24 23:47                             ` Frank Ch. Eigler
2022-12-30 16:44                               ` Mark Wielaard
2023-01-04  8:18                                 ` Mike Frysinger
2023-01-05 22:38                                   ` Mark Wielaard
2023-01-05 22:43                                     ` Mark Wielaard
2023-01-06  6:22                                       ` Joel Brobecker
2023-01-10 18:27                                         ` Frank Ch. Eigler
2023-01-10 20:18                                           ` Mark Wielaard
2023-01-11  5:36                                             ` Joel Brobecker
2023-01-11 23:56                                               ` Mark Wielaard
2023-01-12  5:12                                                 ` broken current onlinedocs Mike Frysinger
2023-01-12  7:30                                                   ` Mark Wielaard
2023-01-16  3:42                                                   ` Joel Brobecker
2023-01-15 22:00                                               ` setting up sim project web space Mike Frysinger
2023-01-16  3:17                                                 ` Joel Brobecker
2021-11-25  2:00                         ` Joel Brobecker
2021-11-28 21:22                           ` Mark Wielaard
2021-12-05 10:51                             ` Joel Brobecker
2021-12-22  7:08                               ` Mike Frysinger
2021-12-24  3:01                                 ` Joel Brobecker

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=YZWjXmevwgS+xbjx@vapier \
    --to=vapier@gentoo.org \
    --cc=overseers@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).