From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19087 invoked by alias); 21 Jul 2009 18:15:25 -0000 Received: (qmail 19071 invoked by uid 22791); 21 Jul 2009 18:15:24 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from rv-out-0708.google.com (HELO rv-out-0708.google.com) (209.85.198.241) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 21 Jul 2009 18:15:16 +0000 Received: by rv-out-0708.google.com with SMTP id b17so814476rvf.48 for ; Tue, 21 Jul 2009 11:15:14 -0700 (PDT) Received: by 10.141.21.3 with SMTP id y3mr3354967rvi.279.1248200113994; Tue, 21 Jul 2009 11:15:13 -0700 (PDT) Received: from hotblack.localnet ([189.4.46.16]) by mx.google.com with ESMTPS id k37sm5350456rvb.20.2009.07.21.11.15.11 (version=SSLv3 cipher=RC4-MD5); Tue, 21 Jul 2009 11:15:12 -0700 (PDT) From: Thiago Jung Bauermann To: Tom Tromey Subject: Re: GSoC Status Report #3 Date: Tue, 21 Jul 2009 18:15:00 -0000 User-Agent: KMail/1.11.4 (Linux/2.6.30-1-amd64; KDE/4.2.4; x86_64; ; ) Cc: Oguz Kayral , gdb ml References: <36a35d480907180812j398bb1ax8889ab1eefca9127@mail.gmail.com> <200907211436.51662.thiago.bauermann@gmail.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200907211516.33161.thiago.bauermann@gmail.com> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-07/txt/msg00168.txt.bz2 Em Terça-feira 21 Julho 2009 13:57:51 Tom Tromey escreveu: > >>>>> "Thiago" == Thiago Jung Bauermann > >>>>> writes: > > Thiago> Just to be clear: the GSoC work is NOT under the Archer > Thiago> umbrella. So it doesn't have to follow the Archer rules. And I > Thiago> strongly prefer that the branch name doesn't start with the > Thiago> archer- prefix. > > That is fine by me. The only reason for the archer- prefix is to avoid > clashes with any branch names from gdb; but probably any name including > "oguz" is also unlikely to cause problems :-) Awesome. What about "gsoc-oguz-python"? I know, creativity in coming up with names is not one of my turn ons... As for branch rules, since this will be Oguz' playground, I guess the only rule is whatever makes him work productively, WDYT? :-) Oguz, there are some git tips in http://sourceware.org/gdb/wiki/ArcherBranchManagement which may help you (e.g., merging from master, extracting a patch, etc.). -- []'s Thiago Jung Bauermann