Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
Subject: Re: RFC: gdb web page patch for git conversion
Date: Mon, 02 Sep 2013 18:18:00 -0000	[thread overview]
Message-ID: <5224D659.2050700@redhat.com> (raw)
In-Reply-To: <20130829205557.GA3315@adacore.com>

On 08/29/2013 09:55 PM, Joel Brobecker wrote:
> Hi Tom,
> 
> On Thu, Aug 29, 2013 at 02:15:38PM -0600, Tom Tromey wrote:
>> Here's the patch I came up with for converting the gdb web pages to git.
> 
> FWIW, it looks good to me.
> 
>> I vaguely remember that there is some other crucial step after
>> committing, maybe in order to push the changes to the FSF?  I don't
>> remember any details about it; so if you know, please respond.
> 
> Yes. Committing to the sourceware CVS automatically gets the sourceware
> web pages updated, but then we need to push the same change to the CVS
> at savannah. I've been doing that by maintaining a git mirror of the CVS
> repo, and cvsexportcommit'ing to both CVS. I can take care of that part.

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...

-- 
Pedro Alves


  reply	other threads:[~2013-09-02 18:18 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 [this message]
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

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=5224D659.2050700@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --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