public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: Joel Brobecker <brobecker@adacore.com>,
	Pedro Alves <pedro@palves.net>,
	Overseers mailing list <overseers@sourceware.org>,
	Mark Wielaard <mark@klomp.org>
Subject: Re: setting up sim project web space
Date: Wed, 4 Jan 2023 03:18:16 -0500	[thread overview]
Message-ID: <Y7U2SBTabZ1AjFo2@vapier> (raw)
In-Reply-To: <f0ce6ccc94b6255f7eaec29d39001a9a2a7f0968.camel@klomp.org>

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

On 30 Dec 2022 17:44, Mark Wielaard wrote:
> On Mon, 2022-10-24 at 19:47 -0400, Frank Ch. Eigler wrote:
> > [...]  it's been over a year since i requested hosting for the GNU
> > > sim, and afaict, gdb is still not prepared to host it.  so what are
> > > the next steps here ?
> > 
> > Sorry, can you remind us what new service you would like?  The sim/
> > sources are still being developed/shipped with gdb, right?

sorry, i'm not subscribed to the overseers group, so i don't see replies
only sent to it.

the sim code is developed in the binutils/gdb monorepo.  it doesn't need
gdb to build ... it works fine all by itself.  i'm not cutting releases
for it today, so most people would get it via gdb releases, or by using
git directly.

> - Part of the online docs are generated by a script
>   /home/gdbadmin/ss/update-web-docs
>   https://www.sourceware.org/gdb/onlinedocs/
>   It isn't clear if this can simply be adapted to also generate the
>   sim documentation. I don't see a
>   doc subdir under sim though, so I am not sure how the sim
>   documentation is generated.

i haven't finished/pushed the manual yet.  i work on it in bursts, and
unfortunately as i write it i find bugs in the sim & underlying projects,
so i work on fixing those so i don't have to document the bugs.

but for the purposes of this discussion, it's a standard texinfo manual
like every other project in the binutils/gdb git tree.  although that
would be just the documentation, not the general project website.

> - The other website files are still in CVS. It would be nice if they
>   could be moved into git. (If we do we have to adjust the above script
>   and cronjobs slightly).
> 
> - The gdb-htdocs repo can only be updated by people in the gdb group
>   (which is a subset of the src group which allows pushing to the
>    binutils-gdb repo). Mike isn't a member of the gdb group, so cannot
>   push to the gdb-htdocs to create a sim subdir there. And it seems the
>   current setup, how and who is in the gdb group and can update the
>   website pages, isn't fully documented.

i guess it boils down to either someone adds me to the gdb group so i
can create a sim/ subspace, or someone sets up a new space that i can
push to.  totally fine to leave it open for other gdb/etc... folks to
push to too (not sure what the acl groups look like).

in either case, i'd like to have https://sourceware.org/sim/ go to the
right place wherever that is.
-mike

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

  reply	other threads:[~2023-01-04  8:18 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
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 [this message]
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=Y7U2SBTabZ1AjFo2@vapier \
    --to=vapier@gentoo.org \
    --cc=brobecker@adacore.com \
    --cc=fche@elastic.org \
    --cc=mark@klomp.org \
    --cc=overseers@sourceware.org \
    --cc=pedro@palves.net \
    /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).