From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6251 invoked by alias); 16 Jan 2015 18:41:11 -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 6229 invoked by uid 89); 16 Jan 2015 18:41:10 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-Spam-User: qpsmtpd, 2 recipients X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Fri, 16 Jan 2015 18:41:09 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t0GIf12w010611 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 16 Jan 2015 13:41:01 -0500 Received: from anchor.twiddle.net (vpn-227-132.phx2.redhat.com [10.3.227.132]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t0GIf1qD003948; Fri, 16 Jan 2015 13:41:01 -0500 Message-ID: <54B95B3B.6010901@redhat.com> Date: Fri, 16 Jan 2015 18:41:00 -0000 From: Richard Henderson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Cary Coutant , "H.J. Lu" CC: Joel Brobecker , Binutils , gdb-patches Subject: Re: Experimental branches References: <20141223132714.GA11973@adacore.com> <20141223180802.GP12884@adacore.com> <20141224002022.GQ12884@adacore.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2015-01/txt/msg00479.txt.bz2 On 01/15/2015 03:04 PM, Cary Coutant wrote: > But I've already pushed several commits onto the upstream branch. > Everything I've read about git says don't rebase if you've already > pushed your branch upstream. That's if you've actually got multiple developers coordinating. For solo development on branches, rebasing minimizes the state difference between trunk and the branch, and so is quite handy (essential?) for preparing to submit a patch set for review. r~