Mailing-List: contact dev-help@streams.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@streams.incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of m.ben.franklin@gmail.com
 designates 209.85.216.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CF7EA395.4A2E%rdouglas@w2odigital.com>
References: <CF7EA395.4A2E%rdouglas@w2odigital.com>
Date: Thu, 24 Apr 2014 13:35:40 -0400
Message-ID: 
 <CAENpzYWMywEZ2r1Mg4aTjr3ma__WitD7WP3Z2x6ti1nT2PJDSg@mail.gmail.com>
Subject: Re: Best way to merge in code
From: Matt Franklin <m.ben.franklin@gmail.com>
To: "dev@streams.incubator.apache.org" <dev@streams.incubator.apache.org>
Content-Type: multipart/alternative; boundary=001a113a970a1b721c04f7cd470f

--001a113a970a1b721c04f7cd470f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

If you have an ICLA on file, then fork and submit a pull request through
git hub.  If not, sign an ICLA and then fork and put a pull request through
git hub :)


On Thu, Apr 24, 2014 at 12:18 PM, Robert Douglas [W2O Digital] <
rdouglas@w2odigital.com> wrote:

> Hi all,
>
> I=E2=80=99ve been working on https://issues.apache.org/jira/browse/STREAM=
S-62 and
> was curious what everyone thought was the best way to go about merging in
> new code. Now that Streams is mirrored on GitHub I can fork that reposito=
ry
> and create a pull request or alternatively I can attach a patch file,
> whichever is easier.
>
> Thanks,
> Robert Douglas
>

--001a113a970a1b721c04f7cd470f--