From: Thomas Schwinge <thomas@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>, Pedro Alves <palves@redhat.com>
Cc: Tom Tromey <tromey@redhat.com>, <gdb-patches@sourceware.org>
Subject: Re: RFC: gdb web page patch for git conversion
Date: Tue, 03 Sep 2013 19:19:00 -0000 [thread overview]
Message-ID: <87eh95hfwa.fsf@kepler.schwinge.homeip.net> (raw)
In-Reply-To: <20130903131803.GA2809@adacore.com>
[-- Attachment #1: Type: text/plain, Size: 892 bytes --]
Hi!
On Tue, 3 Sep 2013 09:18:03 -0400, Joel Brobecker <brobecker@adacore.com> wrote:
> > I'm sure you've thought of that, but I'm curious.
> > Is there any hope in converting those repos away from CVS too at some
> > point? With git (or any DCVS), it sounds like savannah's could just be
> > a clone of sourceware's...
>
> I confess that I never really took any time considering the various
> options for conversion. I update the web sites so seldomly, and
> the CVS-git bridge has been working well enough, so I did not feel
> it was worth much or our time. That being said, I'd be happy to get
> rid of CVS there as well, if that was deemed important.
Last time I looked/asked, the software packages' pages below www.gnu.org
could only be accessed via CVS. (So, for the Hurd I'm also doing this
"[generate HTML files] -> check into CVS dance".)
Grüße,
Thomas
[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]
prev parent reply other threads:[~2013-09-03 19:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 20:15 Tom Tromey
2013-08-29 20:56 ` Joel Brobecker
2013-09-02 18:18 ` Pedro Alves
2013-09-03 13:18 ` Joel Brobecker
2013-09-03 14:44 ` Pedro Alves
2013-09-03 19:07 ` Stan Shebs
2013-09-04 13:09 ` Joel Brobecker
2013-09-04 19:34 ` André Pönitz
2013-09-06 19:50 ` Marc Khouzam
2013-09-03 19:19 ` Thomas Schwinge [this message]
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=87eh95hfwa.fsf@kepler.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=tromey@redhat.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