Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D146A11C35 for ; Fri, 23 May 2014 17:46:43 +0000 (UTC) Received: (qmail 75835 invoked by uid 500); 23 May 2014 17:46:43 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 75752 invoked by uid 500); 23 May 2014 17:46:43 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 75744 invoked by uid 99); 23 May 2014 17:46:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 May 2014 17:46:43 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jesse.k.yates@gmail.com designates 209.85.220.175 as permitted sender) Received: from [209.85.220.175] (HELO mail-vc0-f175.google.com) (209.85.220.175) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 May 2014 17:46:36 +0000 Received: by mail-vc0-f175.google.com with SMTP id id10so3230866vcb.6 for ; Fri, 23 May 2014 10:46:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=y0w1vi+R1yBpSFvD0RuE9Wo8UkIOezcVruoBzdTH+WQ=; b=EvjLhsGCmtA/mCCLE1CPLmudl/NUf3jcfZ/EPmai30LCMX7W2V0iFc+Rhl2/SQdoUf NbIWpeZlUtZf0PM2jzN8avzcfBIG58lSc2VdQaqKHV0a3FiawF4AohHkPfvW7YZiKOlN bPSHRWwdyPiWWVfX1J4fgPLJST0Ola26/EQrmVcqw4uM6V9mXJbuSeQWZGyxR9PRRzjw tPkDsgOlT9ABzfVBEKBV+oB/FcoCNxpVupeewMr+lw4J/aQbqY5j9mZci3EGKhhtgeUn MrsnNvoNWkOOAzcnfjf8nrJM3U8+8wwD7T0mQAb/oCN5HkfaL0AuJXk7rydexu9M8KKE /VAA== MIME-Version: 1.0 X-Received: by 10.58.111.163 with SMTP id ij3mr5591905veb.26.1400867175439; Fri, 23 May 2014 10:46:15 -0700 (PDT) Received: by 10.58.152.71 with HTTP; Fri, 23 May 2014 10:46:15 -0700 (PDT) Received: by 10.58.152.71 with HTTP; Fri, 23 May 2014 10:46:15 -0700 (PDT) In-Reply-To: References: Date: Fri, 23 May 2014 10:46:15 -0700 Message-ID: Subject: Re: [DISCUSSION] Avoiding merge commits From: Jesse Yates To: dev@hbase.apache.org Content-Type: multipart/alternative; boundary=047d7b2e548a5ea55504fa14ce51 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b2e548a5ea55504fa14ce51 Content-Type: text/plain; charset=UTF-8 +1 that's how I do all my git development and what I advocate at salesforce as well. On May 23, 2014 10:39 AM, "Andrew Purtell" wrote: > I recommend we do not push merge commits upstream. I suppose it is easy > enough to filter them out when looking at history but there is no need to > be merging upstream branches into your local tracking branch when you can > rebase instead. In this way we can avoid polluting the history in the > master repository with unnecessary merge commit entries. (And maybe some > devs will be merging upstream into tracking branches or merging commits > from local feature branches several times per day, and these will all > accumulate...) > > When updating your local tracking branch from upstream, use git fetch > upstream && git rebase upstream/branch instead of 'git merge'. > > When developing features on a local branch it's possible to do a squash > commit from the feature branch to the tracking branch using 'git rebase' > instead of 'git merge', then a push of the single squashed commit from the > tracking branch to the upstream branch. > > If these workflow choices are acceptable by consensus we can update the > 'how to commit' document with an illustration of the workflow with example > commands. > > > -- > Best regards, > > - Andy > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > (via Tom White) > --047d7b2e548a5ea55504fa14ce51--