From: Pedro Alves <pedro@palves.net>
To: Mark Wielaard <mark@klomp.org>,
Overseers mailing list <overseers@sourceware.org>,
simon.marchi@polymtl.ca, eliz@gnu.org,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: setting up sim project web space
Date: Fri, 19 Nov 2021 15:49:38 +0000 [thread overview]
Message-ID: <6a72ecd6-1480-1cb8-c223-c6c9d991be2e@palves.net> (raw)
In-Reply-To: <YZeHYvzZd+NTp+yy@vapier>
Joel I think would be the best person to ask about how the GDB website setup works.
I've never touched it myself, so all I learned last time I asked about it, I've since forgot. :-)
Thus, adding Joel.
On 2021-11-19 11:15, Mike Frysinger wrote:
> On 19 Nov 2021 11:08, Mark Wielaard wrote:
>> On Fri, Nov 19, 2021 at 03:42:05AM -0500, Mike Frysinger wrote:
>>>>> It isn't that we don't want to create a new groups cvs/git repo for you
>>>>> to maintain sim documentation, but it is extra work and if it can
>>>>> simply be done as part of the gdb project resources that saves some
>>>>> time for everybody.
>>>>>
>>>>> And maybe if it is a pain for you to maintain the sim webpages as part
>>>>> of gdb, then maybe it is a pain for all of gdb and maybe we should
>>>>> focus on improving that for everybody.
>>>>
>>>> i can start the skeleton under gdb and see how it works. except:
>>>> cvs add: cannot mkdir /cvs/gdb/htdocs/sim: Permission denied
>>>
>>> also, if i'm reading the sources correctly, the gdb manual is not stored in
>>> the gdb cvs tree, but is uploaded manually via scp to the gdbadmin acct.
>>> which i'm pretty sure i wouldn't have access to.
>>>
>>> so are you proposing adding me to the gdb ACLs ?
>>
>> Maybe. I assumed every committer would (technically) be able to update
>> the website, I think it would be good to discusss with the other gdb
>> maintainers. It seems the current setup, how and who can update the
>> gdb website pages, isn't fully documented.
>
> i mean, i don't want these perms. i want hosting for the sim project.
> but i guess i can cc a random selection of global gdb maintainers.
> -mike
>
next prev parent reply other threads:[~2021-11-19 15:49 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 [this message]
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=6a72ecd6-1480-1cb8-c223-c6c9d991be2e@palves.net \
--to=pedro@palves.net \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=mark@klomp.org \
--cc=overseers@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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).