I've been talking with Paul Davis about how we can fix this situation. But no, at the moment, you cannot merge them directly in GitHub. However, while we might advocate RB as the preferred way to submit patches, I do not think we should "lock out" people who prefer to work within the confines of GitHub. This question is not just about "should we get notifications sent". It is more about "should we open this up as a supported channel for receiving contributions?"
On Sun, Oct 7, 2012 at 1:59 AM, Brett Porter <br...@apache.org> wrote: > > On 30/09/2012, at 2:31 AM, Noah Slater <nsla...@tumbolia.org> wrote: > > > Breaking off this question: > > > > On Sat, Sep 29, 2012 at 3:50 PM, Donal Lafferty > > <donal.laffe...@citrix.com>wrote: > > > >> > >> WRT emails for all GIT pulls, wouldn't broadcasting pull requests > clutter > >> the dev mailing list? > > > > > > No, I don't think so. > > > > A GitHub pull request is the same as someone coming to the list and > asking > > us to apply a patch. > > > > If they become a nuisance (what a wonderful problem to have!) we could > > funnel them elsewhere. > > > > PR integration on GitHub will attract a broader base of contributions > from > > the community. > > > > My understanding of the current pull request integration is that > notifications can be sent to the list, but can not be closed or interacted > with on github (other than requesting the original reporter to close them, > or an administrator) - so it's not really integration as much as avoiding > it slipping through the cracks when someone finds the github repo. Is that > still the case? > > Particularly with review board in place, it would seem like getting > notifications of PRs is a good idea, but explicitly encouraging their use > is not. > > - Brett > > > -- NS
