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]
Message-id: <57234D01.90105@samsung.com>
Date:	Fri, 29 Apr 2016 14:01:05 +0200
From:	Krzysztof Kozlowski <k.kozlowski@...sung.com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Olof Johansson <olof@...om.net>, Kevin Hilman <khilman@...nel.org>,
	arm@...nel.org, Kukjin Kim <kgene@...nel.org>,
	linux-arm-kernel@...ts.infradead.org,
	linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>
Subject: Re: [GIT PULL 1/3] ARM: dts: exynos: Secound round of DTS for v4.7

On 04/28/2016 10:37 PM, Arnd Bergmann wrote:
> On Thursday 28 April 2016 21:04:28 Krzysztof Kozlowski wrote:
>> On Thu, Apr 28, 2016 at 04:06:54PM +0200, Arnd Bergmann wrote:
>>> On Wednesday 27 April 2016 11:10:54 Krzysztof Kozlowski wrote:
>>>>   kernel.org:/pub/scm/linux/kernel/git/krzk/linux.git tags/samsung-dt-4.7-2
>>>>
>>>
>>> Pulled into next/dt after I figured out that the URL was wrong.
>>>
>>> Please check your git configuration to make sure you send an address
>>> I can pull from.
>>
>> Ah, indeed, sorry for that. I still did not automate entirely this process
>> so apparently I am doing simple mistakes. I'll be more carefull next
>> time.
> 
> Ok. The trick is to have a separate 'url' and 'pushurl' entry in your
> git config, like
> 
> [remote "origin"]
>         url = git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
>         pushurl = git+ssh://gitolite@...kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
> 
> That way, 'git request-pull' will pick the first one, but 'git push' will
> use the second.

I was using two remotes but your config is easier.

Thanks for hint,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ