Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-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 A507A10D5D for ; Wed, 2 Oct 2013 19:31:55 +0000 (UTC) Received: (qmail 33738 invoked by uid 500); 2 Oct 2013 19:31:55 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 33679 invoked by uid 500); 2 Oct 2013 19:31:55 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 33669 invoked by uid 99); 2 Oct 2013 19:31:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Oct 2013 19:31:55 +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 shazron@gmail.com designates 209.85.216.172 as permitted sender) Received: from [209.85.216.172] (HELO mail-qc0-f172.google.com) (209.85.216.172) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Oct 2013 19:31:50 +0000 Received: by mail-qc0-f172.google.com with SMTP id l13so895769qcy.17 for ; Wed, 02 Oct 2013 12:31:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=/3dmtSCxosBTejxKm2ftchX/kP5gqulFOIREuX/1VM0=; b=Zt2OpubPDGY5FaeNgDN9z05kxQrpea556BgbA2LFXzM+lXpgdwulVuOTUIMr5RhbJG JYJzi8xoeQy2DvooCI5oYr0bV36m8kj1fRe3abqJPh3UeuVDSmf/ynUX0AgEJTDWtIIW 4MBy5hlZnVNdFfcH7c2O+NwWE7zK4tGqTaTPhu/5jAL9rlMhs/GL1o9G3GA2xnYCIhMH u76WFoRpPrDnXusdl4pRbkG/agiKkaTvj9wt3LJmPtrw88VciOBB9Bw9mNCo9dkU0vLj mhOyGxXPJvBGcCPDEh4KDBR67HikxJShwTlDQXF2BY6pVKz/W3CmnjTEA8t+M1ds7R2L 0ouA== X-Received: by 10.224.64.200 with SMTP id f8mr5694190qai.55.1380742290005; Wed, 02 Oct 2013 12:31:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.49.47.106 with HTTP; Wed, 2 Oct 2013 12:30:48 -0700 (PDT) In-Reply-To: References: <967FE4CB-8DDF-4EDD-8282-2D6B0333A005@gmail.com> <506A6C8D-32A4-42C1-BF65-E87FFBBCAAE9@gmail.com> <4E561B73-9D2A-4516-85BF-65195816A7B3@gmail.com> From: Shazron Date: Wed, 2 Oct 2013 12:30:48 -0700 Message-ID: Subject: Re: Tagging 3.1.0 today? To: "dev@cordova.apache.org" , "bowserj@apache.org" Content-Type: multipart/alternative; boundary=001a11c215ccb905b904e7c71d9d X-Virus-Checked: Checked by ClamAV on apache.org --001a11c215ccb905b904e7c71d9d Content-Type: text/plain; charset=ISO-8859-1 I don't think Apache is breaking Git, it's just git. This has happened before, where I commented on the ML about a tag that had the tagged commit missing from any of the branches (I believe it was from a tag from Tim, not calling you out here Tim, but just for precedence purposes as a concrete example for this current issue). I hadn't updated my local cordova-android repo since yesterday. I see that a commit by Joe Bowser with subject "Tagging 3.1.0" with hash 6f17e9fc9cd27f031d94d67fe118008d5f6ec5b3 - this was from the 3.1.0 tag. I searched using git for any local or remote branches (my last Apache fetch) and it did not contain the commit. $ git branch --contains 6f17e9fc9cd27f031d94d67fe118008d5f6ec5b3 (for local branches) $ git branch -a --contains 6f17e9fc9cd27f031d94d67fe118008d5f6ec5b3 (for remote branches) Thus, when someone pulled down the 3.1.x branch, it did not contain your commit. I assume, based on looking at the 3.1.x branch, and not seeing it tagged, that person then tagged it, and it appeared that your commit was removed. The evidence strongly suggests otherwise, imo. I have zipped up my local repo and can provide it to anyone if they want to take a look. On Wed, Oct 2, 2013 at 11:49 AM, Joe Bowser wrote: > On Wed, Oct 2, 2013 at 11:46 AM, Andrew Grieve > wrote: > > Sorry, was away from my computer for a while there. > > > > Joe, sounds like what happened was that you pushed the tag without > pushing > > the branch. That has happened a few times in the past by others > (including > > myself). No biggie. The ASF repos disable git push --force, so I don't > > think it's even possible for tampering to happen. > > I want github back! Apache is breaking git. :( > > As far as tampering, it's totally possible for it to happen. Sadly, > it looks exactly like this. I apologize for getting super aggro about > the git screw-up. > --001a11c215ccb905b904e7c71d9d--