Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755308AbbGZSz5 (ORCPT ); Sun, 26 Jul 2015 14:55:57 -0400 Received: from mail-lb0-f170.google.com ([209.85.217.170]:33992 "EHLO mail-lb0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755242AbbGZSzz (ORCPT ); Sun, 26 Jul 2015 14:55:55 -0400 Date: Sun, 26 Jul 2015 20:37:42 +0200 From: Olof Johansson To: Duc Dang Cc: Loc Ho , Tai Nguyen , "arm@kernel.org" , Linux Kernel Mailing List , "devicetree@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "patches@apm.com" , Jon Masters Subject: Re: [PATCH 0/2 RESEND] power: reset: Add syscon reboot/poweroff device nodes for APM X-Gene platform Message-ID: <20150726183742.GA24272@localhost> References: <1433272747-27114-1-git-send-email-ttnguyen@apm.com> <20150714084004.GA14593@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1594 Lines: 36 On Sat, Jul 25, 2015 at 11:34:42AM -0700, Duc Dang wrote: > Hi Olof, > > We are debating whether we should setup a company server (where we can > have full control about storage, user permissions, backup, ...) or > just use github.com to host our X-Gene kernel tree. > > Github seems already provide everything we need for a public source > tree. Per your experience, what is your (and probably other > maintainers) reference in git hosting server? Is there any > inconvenience or difficulty for the maintainers to pull/merge code > from Github versus from a company server? Hosting on github is fine with us in general. We do prefer to get signed pull requests in particular when they come from other sources than kernel.org, mostly because there's another third party involved in hosting the repo and by using signed tags there's less room for anyone to do bad stuff with the repository without someone noticing. If you host on github, please still use native git pull requests and not the ones that github provides via the web interface. Note however, that given the total volume of patches there's no strong need for you to have a public repo just to send code to us -- we're happy applying patches at the volumes we're currently looking at. I can imagine other reasons for why you would like to have a public repo though. Thanks, -Olof -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/