Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id DEF4A200BEC for ; Thu, 29 Dec 2016 13:21:46 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id DD9EC160B2D; Thu, 29 Dec 2016 12:21:46 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 0DF4C160B15 for ; Thu, 29 Dec 2016 13:21:45 +0100 (CET) Received: (qmail 51739 invoked by uid 500); 29 Dec 2016 12:21:45 -0000 Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@falcon.apache.org Delivered-To: mailing list dev@falcon.apache.org Received: (qmail 51726 invoked by uid 99); 29 Dec 2016 12:21:45 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Dec 2016 12:21:44 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 8DCF8180297 for ; Thu, 29 Dec 2016 12:21:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.879 X-Spam-Level: * X-Spam-Status: No, score=1.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=inmobi.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id aNstOOiDSoIb for ; Thu, 29 Dec 2016 12:21:42 +0000 (UTC) Received: from mail-wj0-f170.google.com (mail-wj0-f170.google.com [209.85.210.170]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 753575FADB for ; Thu, 29 Dec 2016 12:21:42 +0000 (UTC) Received: by mail-wj0-f170.google.com with SMTP id v7so357560032wjy.2 for ; Thu, 29 Dec 2016 04:21:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=inmobi.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=/wr9VpyWc3IBK333rqx/mLCoQxh831UmbOIwBHG+y1o=; b=BvgKDgJmipOrkQgOXrScyz6Y+YmFqbtO4DhykhlsBG2hUm+V6PjShL+Z/ZQVnmMLNX T8daOkrVDV4sUBqM57VAA9AlxvZA835AEFsLn+9brstgrL+Qx9jaHzaqIgph+q/AjkId ULr8qcLGjCM5GGunnCx0ED9GbzA/90CsB28aI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=/wr9VpyWc3IBK333rqx/mLCoQxh831UmbOIwBHG+y1o=; b=CuUenL8Yekeeh6gEkr4nfCEQoYaU609IljMkIKpzIXFuhQ8IhLrYgdsUiAgIGP5Ur0 NLpvGsUnINB7hX7Dl8RuzL2a+6z/7XkKLG8eFnd+VLSGabbYfqyeHRBtgj7AqSQncaiH bFBfzntPdkk3SqdVArp0K44HGESutSdBK3DCpQblbHeFSo9AaEMt4n/ylFd35xEsh9nX KyzD8CUMaD3elWGrD4um6D12CBH2PLytb8rN2xdkrPkCSE3VooHS4YfH1wCKafN0D+N8 kbuoiesfBdcK+xBY6R7eA4jysEuzpY9SNUw1pWokOriujrZ97XaWYqItTpZtcqGHvXw/ bD+w== X-Gm-Message-State: AIkVDXJ8tVz5ziGiR14JITZPfx0KiuYDocUb1NT81hqCwbe8QnJmtXTmAl8b+A2JWo7BU+yY7Mtt20QuYOyXFyWbMCIqd2HGIaCyGf/x1sdBx2UHAi51TXrmWAVfhWIiM0UiWfBzWHu1PLrJUQ== X-Received: by 10.194.5.165 with SMTP id t5mr39860748wjt.107.1483014101188; Thu, 29 Dec 2016 04:21:41 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.150.133 with HTTP; Thu, 29 Dec 2016 04:21:40 -0800 (PST) In-Reply-To: References: From: Praveen Adlakha Date: Thu, 29 Dec 2016 17:51:40 +0530 Message-ID: Subject: Re: Squashing commits before git push To: dev@falcon.apache.org Content-Type: multipart/alternative; boundary=047d7b5d8671b3a0350544cb2081 archived-at: Thu, 29 Dec 2016 12:21:47 -0000 --047d7b5d8671b3a0350544cb2081 Content-Type: text/plain; charset=UTF-8 I misread it. +1 for this. On Thu, Dec 29, 2016 at 5:22 PM, Praveen Adlakha wrote: > I believe we should be doing a rebase rather than pull and making a merge > commit. > > As far as 1 commit per pull request is concerned we should allow multiple > commits as for the reviewer it becomes easy to review only the latest > commit rather than re-reviewing the older commits. > > > > On Thu, Dec 29, 2016 at 4:53 PM, Pracheer Agarwal < > pracheeragarwal@gmail.com> wrote: > >> +1 >> >> On Thu, Dec 29, 2016 at 4:53 PM, Sandeep Samudrala >> wrote: >> >> > Makes sense. >> > >> > On Thu, Dec 29, 2016 at 3:55 PM, Pallavi Rao >> > wrote: >> > >> > > While creating a PR, we tend to push the local commits as is when we >> do a >> > > git push into the forked repo. These local commits include lot of >> merge >> > > commits, and intermediate commits. This makes it hard to review, when >> > some >> > > changes have been requested (as the reviewer has to either look at >> > changes >> > > made to each commit, or re-review the whole patch). >> > > >> > > Would like to request contributors to squash the new commits into one >> > > before they do a git push, so, all your intermediate changes go in as >> one >> > > commit. Basically, resulting 1 commit per update to PR. >> > > >> > > >> > > Thoughts? >> > > >> > > -- >> > > _____________________________________________________________ >> > > The information contained in this communication is intended solely for >> > the >> > > use of the individual or entity to whom it is addressed and others >> > > authorized to receive it. It may contain confidential or legally >> > privileged >> > > information. If you are not the intended recipient you are hereby >> > notified >> > > that any disclosure, copying, distribution or taking any action in >> > reliance >> > > on the contents of this information is strictly prohibited and may be >> > > unlawful. If you have received this communication in error, please >> notify >> > > us immediately by responding to this email and then delete it from >> your >> > > system. The firm is neither liable for the proper and complete >> > transmission >> > > of the information contained in this communication nor for any delay >> in >> > its >> > > receipt. >> > > >> > >> > > -- _____________________________________________________________ The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. The firm is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt. --047d7b5d8671b3a0350544cb2081--