public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Mark Wielaard <mark@klomp.org>
Cc: gdb@sourceware.org
Subject: Re: setting up sim project web space
Date: Wed, 17 Nov 2021 19:19:01 -0500	[thread overview]
Message-ID: <YZWb9amjJmvF4NK/@vapier> (raw)
In-Reply-To: <YZVOB8WbkXe6pmVz@wildebeest.org>

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

On 17 Nov 2021 19:46, Mark Wielaard wrote:
> On Wed, Nov 17, 2021 at 12:27:41PM -0500, Mike Frysinger via Gdb wrote:
> > i'd like to start a sim landing page for the sim project at
> > https://sourceware.org/sim/
> > 
> > i'm not sure how to actually do this.  i tried e-mailing overseers but
> > didn't get a response.  anyone know where to start ?
> 
> I can setup a sim-htdocs git repo for you, if you want, but I need to
> know which project/group is responsible for that.  Mailing overseers
> is the right way.  There was actually a reply to your request which
> you might have misssed:
> https://sourceware.org/pipermail/overseers/2021q3/017708.html
> 
> Could you reply to that?  I think people are just wondering how/why the
> webpages need to be separate from the other gdb webpages on sourceware.

i'm guessing Frank didn't reply-all, he just posted to the list.  i thought
overseers was an alias, not a list anyone could subscribe to, so i missed
the response.  i'll follow up there once i figure out how to download the
raw e-mail :).  thanks.

the existence of the group is a bit hard to find -- it doesn't really show
up in searches.
https://sourceware.org/cgi-bin/search.cgi?submit=Search%3A&q=overseers
-mike

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

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17 17:27 Mike Frysinger
2021-11-17 18:46 ` Mark Wielaard
2021-11-18  0:19   ` Mike Frysinger [this message]
     [not found] <YZeHYvzZd+NTp+yy@vapier>
     [not found] ` <6a72ecd6-1480-1cb8-c223-c6c9d991be2e@palves.net>
     [not found]   ` <YZpQsaSI9EyvwoLs@adacore.com>
     [not found]     ` <ca4fd206bd854a3613bd54a7af4c4ad6534534b2.camel@klomp.org>
     [not found]       ` <YZ4e/i9H0BELlV0r@vapier>
     [not found]         ` <Y1a6/JlhRSgfVEx2@vapier>
     [not found]           ` <Y1ckAXF+qMU2qM7J@elastic.org>
     [not found]             ` <f0ce6ccc94b6255f7eaec29d39001a9a2a7f0968.camel@klomp.org>
     [not found]               ` <Y7U2SBTabZ1AjFo2@vapier>
     [not found]                 ` <20230105223840.GI8237@gnu.wildebeest.org>
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-15 22:00                             ` Mike Frysinger
2023-01-16  3:17                               ` 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=YZWb9amjJmvF4NK/@vapier \
    --to=vapier@gentoo.org \
    --cc=gdb@sourceware.org \
    --cc=mark@klomp.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).