Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
MIME-Version: 1.0
Date: Fri, 17 Oct 2014 08:44:39 +0100
Message-ID: 
 <CABeJX=1WEM5_7C0c=XhB1n433W1SpnGJihO1jZOuhcPvJ1g2WQ@mail.gmail.com>
Subject: [ALL] How to handle GitHub pull requests
From: Duncan Jones <djones@apache.org>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=UTF-8

Hi everyone,

Some of our contributors like to use GitHub pull requests (PRs) as a
means of providing patches. Until now, I've tended to access the
.patch version of these pull requests and apply them in SVN.

Is there a preferred approach to take here? I have a GitHub account,
so presumably I could be given rights to the repositories I commit to
(lang) and this would allow me to merge PRs directly into trunk. Would
such changes be reflected in our SVN code-base too? Is there any
advantage to one approach over the other?

Apologies if this has already been discussed at length before - I
searched the mail archives but didn't come up with anything other than
passing references to our GitHub repositories.

Kind regards,

Duncan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org