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:	Mon, 18 Jan 2016 09:49:11 +0200
From:	Tomi Valkeinen <tomi.valkeinen@...com>
To:	Al Viro <viro@...IV.linux.org.uk>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [git pull] vfs.git regression fix


On 16/01/16 15:44, Al Viro wrote:

> FWIW, the main inconvenience with git request-pull is that it still needs
> s/gitolite@...kernel.org:/git:\/\/git.kernel.org/ postprocessing.  It mimics
> the git push, but the remote you are pushing to probably won't be usable for
> pulling by others.  Looks like it would be useful to have something like
> 	pull_url = git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git
> to go with
> 	url = gitolite@...kernel.org:/pub/scm/linux/kernel/git/viro/vfs.git
> in .git/config, settable by something in git remote.  OTOH, it's possible to
> emulate by setting an extra remote and using git push vfs <...> for pushes,
> while doing git request-pull origin vfs-pull <...> for pull requests...
 
Isn't "pushurl" for that? I have:

[remote "origin"]
        url = git://git.kernel.org/pub/scm/linux/kernel/git/tomba/linux.git
        pushurl = gitolite.kernel.org:/pub/scm/linux/kernel/git/tomba/linux.git
        fetch = +refs/heads/*:refs/remotes/origin/*

 Tomi


Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ