From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: Alan Hayward <Alan.Hayward@arm.com>,
Simon Marchi <simon.marchi@ericsson.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
nd <nd@arm.com>
Subject: Re: [PATCH] Replace contribution list in CONTRIBUTE file with wiki link
Date: Fri, 25 Jan 2019 06:08:00 -0000 [thread overview]
Message-ID: <20190125060831.GD7566@adacore.com> (raw)
In-Reply-To: <f31cdd09-2c4d-cfbc-d1ac-cd0752034941@redhat.com>
> That has been the (mental) blocker for me thus far. The webpages are
> still in CVS somewhere. I never touched it myself.
> Joel, can you guide us here?
There are two CVS repositories as you mentioned. One is on sourceware
(sourceware.org:/cvs/gdb/htdocs), and one is on Savannah. For now,
it is easier for me if you just send me the patch you want to commit,
and I do it. Otherwise, the re-synchronization on my end can be painful.
> AFAIK the current process is that commits go to both sourceware.org's CVS and
> to another copy in gnu.org as well for the https://www.gnu.org/software/gdb/ .
> I had chatted with Joel at the Cauldron about streamlining this, and the
> conclusion seemed to be that there's no real blocker for making the gnu.org
> version simply a redirect to sourceware.org. That would simplify things. The
> other neat step would be to migrate to git. :-)
Do you guys know who to ask to get the redirection?
And before we do, should we perhaps consider the opposite redirection?
In other words, redirect from sourceware.org to gnu.org/software/gdb?
One strong requirement before we can consider it is that Savannah first
support git repositories. It seems to be possible:
https://savannah.gnu.org/maintenance/UsingGit/
The secondary problem would then become - figuring out how to
automate the auto-update of the website upon pushing new changes.
The redirect to sourceware might make things easier, but it would
be a one-off action item, and then things would be on the GNU server.
Just not the best time for me to take on another task, unfortunately
:-(.
In the meantime, I'm happy to push changes sent to me. That part
just takes a couple of minutes each time.
--
Joel
next prev parent reply other threads:[~2019-01-25 6:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 9:46 Alan Hayward
2019-01-23 15:21 ` Simon Marchi
2019-01-23 16:03 ` Pedro Alves
2019-01-23 17:15 ` Alan Hayward
2019-01-24 13:00 ` Pedro Alves
2019-01-25 6:08 ` Joel Brobecker [this message]
2019-01-25 14:30 ` Alan Hayward
[not found] ` <e9019e9b-f57b-26e8-1d53-2736798787e0@redhat.com>
2019-01-26 6:26 ` Joel Brobecker
2019-01-28 10:02 ` Alan Hayward
2019-01-28 19:50 ` Pedro Alves
2019-01-29 5:33 ` 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=20190125060831.GD7566@adacore.com \
--to=brobecker@adacore.com \
--cc=Alan.Hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.com \
--cc=palves@redhat.com \
--cc=simon.marchi@ericsson.com \
/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