Return-Path: X-Original-To: apmail-accumulo-dev-archive@www.apache.org Delivered-To: apmail-accumulo-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 DB82610AD0 for ; Thu, 13 Jun 2013 01:05:38 +0000 (UTC) Received: (qmail 1648 invoked by uid 500); 13 Jun 2013 01:05:38 -0000 Delivered-To: apmail-accumulo-dev-archive@accumulo.apache.org Received: (qmail 1623 invoked by uid 500); 13 Jun 2013 01:05:38 -0000 Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@accumulo.apache.org Delivered-To: mailing list dev@accumulo.apache.org Received: (qmail 1615 invoked by uid 99); 13 Jun 2013 01:05:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Jun 2013 01:05:38 +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 (nike.apache.org: domain of drew.farris@gmail.com designates 209.85.128.182 as permitted sender) Received: from [209.85.128.182] (HELO mail-ve0-f182.google.com) (209.85.128.182) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Jun 2013 01:05:31 +0000 Received: by mail-ve0-f182.google.com with SMTP id ox1so7321668veb.13 for ; Wed, 12 Jun 2013 18:05:10 -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=OE5nuKVnq7/qc3BuG6MFnWUIbXjOsKxZYtHnKzS6DI4=; b=tuzz6JDW7XQs8w+lHmY5m/XpxOnvQnV/FIvsuHhribYk162ANiClxlFG7ZSoqwUqQe //215q5m4i+ot1BGkQ10T9EZqqQwQ3ebE3Np+Es+mrYn9jdTE6notbIvl4GO7/opcJkx NEqYhIJufD3ADQj3Q1FA0HcsiYbjK/+M9JyVVwwqBQ/BUgIceP3KmHjpOHs8MhZNnObO VWAlhqE+ouge/G+rF5Y0XHBJTxbKJVh6xBF3kpa+2hE4rP104lCcLQk/Ex+DvN7YvOtv TlL9XnKRq4f5OFjCozxmQUuIquXqb/Y9oPI1lP0jXa8CxKupijonJb+cnjB/o7XW5wdM nF2A== MIME-Version: 1.0 X-Received: by 10.220.205.67 with SMTP id fp3mr10632077vcb.43.1371085510570; Wed, 12 Jun 2013 18:05:10 -0700 (PDT) Received: by 10.58.223.103 with HTTP; Wed, 12 Jun 2013 18:05:10 -0700 (PDT) In-Reply-To: References: <51AEAAD0.9020902@gmail.com> <51AFECB5.9010901@gmail.com> <51B68F00.6020904@gmail.com> Date: Wed, 12 Jun 2013 21:05:10 -0400 Message-ID: Subject: Re: [git] Documentation and Plan of Action From: Drew Farris To: "dev@accumulo.apache.org" Content-Type: multipart/alternative; boundary=001a11c32386d0af5904defeb8e6 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c32386d0af5904defeb8e6 Content-Type: text/plain; charset=ISO-8859-1 Josh, Chris, Mike, thanks for hashing this out. The document is long, but I believe it contains the appreciate level of detail so as to eliminate many ambiguities/questions as to how things are done. I have a couple questions. From the docs: " Whatever the actual case is, the developer who made the first set of changes (you) is the one responsible for performing the merge through the rest of the active versions. Even when the merge may results in a zero-length change in content, this is incredibly important to record as you are the one who knows that this zero-length change in content is correct!" Sorry for the newb question, but how does one actually create zero length commit? Also, I have encountered cases where a merge has pulled in changes from previous branches that were unrelated to the particular changes I am trying to merge upwards. I suspect this has something to do with the fact that someone else has done something wrong (eg: neglected to merge their change). What is the appropriate approach to resolving this issue? Drew --001a11c32386d0af5904defeb8e6--