From: Stan Shebs <stanshebs@earthlink.net>
To: gdb-patches@sourceware.org
Subject: Re: RFC: gdb web page patch for git conversion
Date: Tue, 03 Sep 2013 19:07:00 -0000 [thread overview]
Message-ID: <52263373.3080401@earthlink.net> (raw)
In-Reply-To: <5225F5D2.3050509@redhat.com>
On 9/3/13 7:44 AM, Pedro Alves wrote:
> On 09/03/2013 02:18 PM, Joel Brobecker 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.
>
> Ack. I'll admit that my curiosity stems from the fact that
> I've myself considered tweaking the web pages before, but never
> managed to get myself over the fact that that would involve
> another cvs checkout. :-) I'll admit it sounds silly for
> someone who's been using cvs day in, day out. Maybe that's
> just my unconscious telling me to avoid touching html. :-)
>
My semi-baked plan for the web site redesign, as seen at
http://sourceware.org/gdb/wiki/WebsiteRedesign
includes a git migration.
Stan
stan@codesourcery.com
next prev parent reply other threads:[~2013-09-03 19:07 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 [this message]
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
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=52263373.3080401@earthlink.net \
--to=stanshebs@earthlink.net \
--cc=gdb-patches@sourceware.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