Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
Received-SPF: error (nike.apache.org: encountered temporary error during SPF
 processing of domain of mberman@sqrrl.com)
MIME-Version: 1.0
In-Reply-To: 
 <CAA+ACqccnEDsd9Z3cz3GP7bapX_Hi45uS4YcOBnc2UN2FqBJ5Q@mail.gmail.com>
References: 
 <CAA+ACqccnEDsd9Z3cz3GP7bapX_Hi45uS4YcOBnc2UN2FqBJ5Q@mail.gmail.com>
From: Michael Berman <mberman@sqrrl.com>
Date: Thu, 1 Aug 2013 17:17:23 -0400
Message-ID: 
 <CAA+ACqcLz8ESDHsb-143PZ4NqCsk-dV2_kMTDnx6WZnQ-QtG+g@mail.gmail.com>
Subject: Re: github mirror
To: dev <dev@accumulo.apache.org>
Content-Type: multipart/alternative; boundary=e89a8ff1cece752e9704e2e95fd2

--e89a8ff1cece752e9704e2e95fd2
Content-Type: text/plain; charset=ISO-8859-1

Oh, actually I was looking at the wrong branch.  It's only a month old, not
a year old...but my question remains.


On Thu, Aug 1, 2013 at 5:15 PM, Michael Berman <mberman@sqrrl.com> wrote:

> Does anyone know what the process is for getting the github mirror pointed
> to the real git repo? Right now it's pointing at a year-old revision off
> SVN.  I'd like to fork a branch for my SSL work so I can submit pull
> requests back, but it doesn't seem like there's a point if it's so far
> diverged from master.
>

--e89a8ff1cece752e9704e2e95fd2--