From patchwork Fri Mar 2 14:10:42 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Tobias Burnus X-Patchwork-Id: 144266 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) by ozlabs.org (Postfix) with SMTP id E45F4B6EEC for ; Sat, 3 Mar 2012 01:11:15 +1100 (EST) Comment: DKIM? See http://www.dkim.org DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=gcc.gnu.org; s=default; x=1331302277; h=Comment: DomainKey-Signature:Received:Received:Received:Received: Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject: References:In-Reply-To:Content-Type:Mailing-List:Precedence: List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help:Sender: Delivered-To; bh=v8ye1m64qvlGrRBCRki4DkNNpf8=; b=jZTwBryn28VV1Z+ sPWH2qAvIz32aO3GlOJj4qVmJ4tS8gyXqA++NwVpYl8jJK75WixiiohGrL8Iha0k eRXhaU+G69oGkVgsb1x+3qav1Ztc4mTkj3b0ZWjTZAmcuhV//qv1vL17vnt1AUs8 /hvUWO+St8Uutm6jQnS/dIeScQaA= Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=gcc.gnu.org; h=Received:Received:X-SWARE-Spam-Status:X-Spam-Check-By:Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Mailing-List:Precedence:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help:Sender:Delivered-To; b=CuDNnzXIzHqtXczoCmdInpTMPcp6MtMurCAezpZ8xKQ8bBtOG7GG0/ya4E3kFh EcZW69aKmZLI2fWnCRS8YRGUYAmLTE8bnStf7RGmjX5Bptc+z08yAXzJ6TiUkHAP Q8TCjuX2PhVOmotGl1XWU/NZ34rS+gNVK6gIwEZtE3bO8=; Received: (qmail 8267 invoked by alias); 2 Mar 2012 14:11:00 -0000 Received: (qmail 8258 invoked by uid 22791); 2 Mar 2012 14:10:58 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL, BAYES_00, RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org Received: from mx01.qsc.de (HELO mx01.qsc.de) (213.148.129.14) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 02 Mar 2012 14:10:45 +0000 Received: from [192.168.178.22] (port-92-204-104-94.dynamic.qsc.de [92.204.104.94]) by mx01.qsc.de (Postfix) with ESMTP id C62373D325; Fri, 2 Mar 2012 15:10:42 +0100 (CET) Message-ID: <4F50D4E2.8090006@net-b.de> Date: Fri, 02 Mar 2012 15:10:42 +0100 From: Tobias Burnus User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120215 Thunderbird/10.0.2 MIME-Version: 1.0 To: Jakub Jelinek CC: gcc patches Subject: Re: [wwwdocs] releasing.html: Git - mirror new branch References: <4F50D26C.7060206@net-b.de> <20120302140258.GB18768@tyan-ft48-01.lab.bos.redhat.com> In-Reply-To: <20120302140258.GB18768@tyan-ft48-01.lab.bos.redhat.com> Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Delivered-To: mailing list gcc-patches@gcc.gnu.org On 03/02/2012 03:02 PM, Jakub Jelinek wrote: > releasing.html is wrong for this, it has nothing to do with releasing, > but with branching, so something like that should go into > branching.html instead. From this isn't clear where this command needs > to be run, btw, on gcc.gnu.org directly, somewhere else? Thanks for the comments - I unfortunately saw them only just after Richard's OK. How about the following? Tobias Index: releasing.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/releasing.html,v retrieving revision 1.37 diff -u -r1.37 releasing.html --- releasing.html 2 Mar 2012 14:04:38 -0000 1.37 +++ releasing.html 2 Mar 2012 14:08:28 -0000 @@ -55,12 +55,6 @@
  • Reenable the generation of snapshots off the respective release branch in the crontab of gccadmin on gcc.gnu.org.
    • - -
  • For a new major release, add the release to GIT mirror; example: -
    -$ cd /git/gcc.git/.git
-$ git symbolic-ref refs/heads/gcc-4_7-branch refs/remotes/gcc-4_7-branch
-

    • Web Site Updates

    Index: branching.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/branching.html,v retrieving revision 1.30 diff -u -r1.30 branching.html --- branching.html 20 Nov 2010 15:15:51 -0000 1.30 +++ branching.html 2 Mar 2012 14:08:28 -0000 @@ -23,6 +23,17 @@
  • Update the file gcc/BASE-VER on the mainline, to use the next major release number (e.g., 3.2 instead of 3.1).
    • +
  • Update the GIT mirror by running on gcc.gnu.org the +following command, substituting appropriate version +numbers: +
    +
    +$ cd /git/gcc.git/.git
+$ git symbolic-ref refs/heads/gcc-4_7-branch refs/remotes/gcc-4_7-branch
+
    +
    +
    • +
  • Create a new htdocs/gcc-VERSION directory for the next major release in the wwwdocs repository and populate it with initial copies of changes.html and