From: Mark Wielaard <mark@klomp.org>
To: "Frank Ch. Eigler" <fche@elastic.org>,
Joel Brobecker <brobecker@adacore.com>,
Pedro Alves <pedro@palves.net>,
Overseers mailing list <overseers@sourceware.org>
Cc: Mike Frysinger <vapier@gentoo.org>
Subject: Re: setting up sim project web space
Date: Fri, 30 Dec 2022 17:44:58 +0100 [thread overview]
Message-ID: <f0ce6ccc94b6255f7eaec29d39001a9a2a7f0968.camel@klomp.org> (raw)
In-Reply-To: <Y1ckAXF+qMU2qM7J@elastic.org>
Hi Mike, other gdb hackers,
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?
So last time there were a couple of issues:
- There were two places the gdb webpages were kept.
This has been resolved by Joel now https://www.gnu.org/software/gdb
redirects to https://sourceware.org/gdb
- 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.
- 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.
Cheers,
Mark
next prev parent reply other threads:[~2022-12-30 16:45 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 [this message]
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=f0ce6ccc94b6255f7eaec29d39001a9a2a7f0968.camel@klomp.org \
--to=mark@klomp.org \
--cc=brobecker@adacore.com \
--cc=fche@elastic.org \
--cc=overseers@sourceware.org \
--cc=pedro@palves.net \
--cc=vapier@gentoo.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).