From patchwork Fri Mar 2 14:00:12 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Tobias Burnus X-Patchwork-Id: 144264 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 D70B4B6EF1 for ; Sat, 3 Mar 2012 01:00:40 +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=1331301642; h=Comment: DomainKey-Signature:Received:Received:Received:Received: Message-ID:Date:From:User-Agent:MIME-Version:To:Subject: Content-Type:Mailing-List:Precedence:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:Sender:Delivered-To; bh=NrJeMkP 8Mgw60MJV64mDFJY5iLk=; b=LxlM1smdiFuPq5x7TXjIaqRxgs0nR86P+W+0Cy0 6B91xdc3jdWy5q6tu1x+QqaFyUPm8viRO40VEhfQGr6c7U7WLmoxYo6uXSbSiCdE lxLaNDK8s7FHMzQcUgcj9AMmQ2mciapXXH9y4+SxuuMuAV6mGbS3TtZhJGIDk9fe Xv9E= 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:Subject:Content-Type:Mailing-List:Precedence:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help:Sender:Delivered-To; b=HWTpyg/g2i155krLsaIlOUQ/kBo1ExY3y1vzgkE6zo0H/220z1R142xcDKF+mF YM6CBVns0RjwSU5vQn2r3tN/ZRBxxqaFP8wBM//j8CZBc//Od8LR47ohd7WO0cXX MTHSieJcTjVLnDNkT0JDEqlEwUi8ACu28yOapEqnFTy8s=; Received: (qmail 918 invoked by alias); 2 Mar 2012 14:00:31 -0000 Received: (qmail 900 invoked by uid 22791); 2 Mar 2012 14:00:28 -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 mx02.qsc.de (HELO mx02.qsc.de) (213.148.130.14) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 02 Mar 2012 14:00:15 +0000 Received: from [192.168.178.22] (port-92-204-104-94.dynamic.qsc.de [92.204.104.94]) by mx02.qsc.de (Postfix) with ESMTP id E06421E384; Fri, 2 Mar 2012 15:00:13 +0100 (CET) Message-ID: <4F50D26C.7060206@net-b.de> Date: Fri, 02 Mar 2012 15:00:12 +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: gcc patches Subject: [wwwdocs] releasing.html: Git - mirror new branch 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 As mentioned on #gcc, the git mirror should also include new major releases. Diego also documented it on the wiki: http://gcc.gnu.org/wiki/GitMirror#Adding_a_branch_to_origin.2BAC8.2A (Wiki page rev. 94 -> 96) OK for committal? Tobias Index: releasing.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/releasing.html,v retrieving revision 1.36 diff -u -r1.36 releasing.html --- releasing.html 1 Mar 2012 13:16:51 -0000 1.36 +++ releasing.html 2 Mar 2012 13:55:52 -0000 @@ -55,6 +55,12 @@
  • 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