From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@palves.net>
Cc: 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: Sun, 21 Nov 2021 17:59:13 +0400 [thread overview]
Message-ID: <YZpQsaSI9EyvwoLs@adacore.com> (raw)
In-Reply-To: <6a72ecd6-1480-1cb8-c223-c6c9d991be2e@palves.net>
> 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.
I see some head shaking in my future...
The GDB website is under CVS, and there are two copies.
- One is hosted on GNU Savannah
https://savannah.gnu.org/projects/gdb
This is the source of the website that's published on gnu.org:
https://www.gnu.org/software/gdb/
- One is hosted on sourceware.org
CVS/Root: sourceware.org:/cvs/gdb
CVS/Repository: htdocs
This repository is the source of the copy on sourceware.org:
https://www.sourceware.org/gdb/
I don't know why we have two copies of the website, unfortunately.
It would be nice if we could transition the sources to Git.
I haven't done it, because I don't know how the automatic-update-after-push
is set up, so I'm concerned about breaking the website update if I do.
Meanwhile, because I've pretty much been the only editor of those
sources, I've been able to get away with my own Git repository and
the use of "git cvsexportcommit" to push patches.
If people send me patches, I'm happy to push them.
--
Joel
next prev parent reply other threads:[~2021-11-21 13:59 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 [this message]
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=YZpQsaSI9EyvwoLs@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=mark@klomp.org \
--cc=overseers@sourceware.org \
--cc=pedro@palves.net \
--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).