Return-Path: X-Original-To: apmail-jclouds-dev-archive@minotaur.apache.org Delivered-To: apmail-jclouds-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CB4D417566 for ; Sun, 5 Oct 2014 20:29:57 +0000 (UTC) Received: (qmail 55698 invoked by uid 500); 5 Oct 2014 20:29:57 -0000 Delivered-To: apmail-jclouds-dev-archive@jclouds.apache.org Received: (qmail 55640 invoked by uid 500); 5 Oct 2014 20:29:57 -0000 Mailing-List: contact dev-help@jclouds.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jclouds.apache.org Delivered-To: mailing list dev@jclouds.apache.org Received: (qmail 55626 invoked by uid 99); 5 Oct 2014 20:29:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Oct 2014 20:29:57 +0000 X-ASF-Spam-Status: No, hits=3.3 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS,URIBL_SBL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of adrian.f.cole@gmail.com designates 209.85.214.174 as permitted sender) Received: from [209.85.214.174] (HELO mail-ob0-f174.google.com) (209.85.214.174) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Oct 2014 20:29:31 +0000 Received: by mail-ob0-f174.google.com with SMTP id wp18so3052921obc.33 for ; Sun, 05 Oct 2014 13:29: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:date:message-id:subject:from:to :content-type; bh=2jgoOi0LT6mjPR574o8WswkypjbVk3pQ0Nua0ooWlaw=; b=hzpk4OJ3/kSL2Fq91/kCOtN7nN1leO1yYfDIMG8bgjcfvkrL7cWYOaJvNQ/Erz4MDH yEgueL5eahbAfwktZiUQrr0NsxKmxt5YN4KsGMwd6/qSfNAjC/q+c52FZGYKr7R1Yp7E MXOZVCmSCUXIrd8WYwuRt/UjctxaetxGloLflJtczv1UKmGcXUF65Amg7MvLHWIUQGuM 6S1N7Kw7ci/yya8fpDmz2yTzB8oYUMhpiWsxLfYdoS6+JrI4nXh/RSsaB1ENiJj59vrq QUgZFpxCtfFbIvUKdm4AfU0mUOsYANxaPAxlb2Euw7PEiLWq7TYoBorzMKjWSaqC4vQ3 WA7w== MIME-Version: 1.0 X-Received: by 10.60.58.36 with SMTP id n4mr4583132oeq.73.1412540970561; Sun, 05 Oct 2014 13:29:30 -0700 (PDT) Received: by 10.202.17.132 with HTTP; Sun, 5 Oct 2014 13:29:30 -0700 (PDT) In-Reply-To: <20141005222631.9m3ushtlpcg8gw4w@webmail.qrmedia.com> References: <20141005204931.8rqnhjy2owg8wwog@webmail.qrmedia.com> <20141005215306.fo6ai23eo0gksc80@webmail.qrmedia.com> <20141005222631.9m3ushtlpcg8gw4w@webmail.qrmedia.com> Date: Sun, 5 Oct 2014 13:29:30 -0700 Message-ID: Subject: Re: unhook unmaintained providers from master From: Adrian Cole To: dev@jclouds.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org Is this necessary? I think we are cart before horse, debating SEO friendliness of how to find a commit id. It is a rare case that anyone helps on old providers anyway (who would be looking for that commit). If they can't find it from git log or jiras, I'm sure someone else on the dev team could, right? -A On Sun, Oct 5, 2014 at 1:26 PM, Andrew Phillips wrote: >> sounds like a job for jira. add a jira to kill the provider, tag that >> jira in the commit. Then either via jira or git log, it is clear when >> it happened and the single commit that could possibly be reverted. > > > +1 for using JIRA to record the details. I don't know how well searchable > JIRA is, though - it would be nice if someone searching for "jclouds > " in a search engine would be able to find a link to > that commit... > > ap