lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Fri, 28 Aug 2015 13:06:34 -0700
From:	Olof Johansson <olof@...om.net>
To:	Duc Dang <dhdang@....com>
Cc:	Loc Ho <lho@....com>, Tai Nguyen <ttnguyen@....com>,
	"arm@...nel.org" <arm@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"patches@....com" <patches@....com>, Jon Masters <jcm@...hat.com>
Subject: Re: [PATCH 0/2 RESEND] power: reset: Add syscon reboot/poweroff
 device nodes for APM X-Gene platform

Hi,

On Fri, Aug 28, 2015 at 1:00 PM, Duc Dang <dhdang@....com> wrote:
> On Sun, Jul 26, 2015 at 11:37 AM, Olof Johansson <olof@...om.net> wrote:
>>
>> 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.
>
> Hi Olof,
>
> I have APM X-Gene git ready on github. According to your response
> above, I need to
> send a signed pull request. I created a PGP key on public server
> (https://pgp.mit.edu/pks/lookup?search=duc+dang&op=index) and signed the tag on
> APM X-Gene tree with my key.
>
> Please let me know if I need anything else before sending the git pull
> request to you.
> My key is not signed by any maintainer yet, would you mind to arrange some
> time next week to meet and help sign my key as well?

Yeah, I can do that, and you can get more signatures at Linaro Connect
in case you're attending.

(let's sort out details off-list).


-Olof
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ