From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10576 invoked by alias); 2 Sep 2013 18:18:08 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 10564 invoked by uid 89); 2 Sep 2013 18:18:08 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 02 Sep 2013 18:18:08 +0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-5.8 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r82II5Ma029526 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 2 Sep 2013 14:18:05 -0400 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r82II100003040; Mon, 2 Sep 2013 14:18:02 -0400 Message-ID: <5224D659.2050700@redhat.com> Date: Mon, 02 Sep 2013 18:18:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 To: Joel Brobecker CC: Tom Tromey , gdb-patches@sourceware.org Subject: Re: RFC: gdb web page patch for git conversion References: <87ob8gp82d.fsf@fleche.redhat.com> <20130829205557.GA3315@adacore.com> In-Reply-To: <20130829205557.GA3315@adacore.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SW-Source: 2013-09/txt/msg00041.txt.bz2 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