From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bear.ext.ti.com ([192.94.94.41]:46822 "EHLO bear.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753778AbcARHtP (ORCPT ); Mon, 18 Jan 2016 02:49:15 -0500 Subject: Re: [git pull] vfs.git regression fix To: Al Viro References: <20160115201810.GF17997@ZenIV.linux.org.uk> <20160115210046.GG17997@ZenIV.linux.org.uk> <20160116134458.GK17997@ZenIV.linux.org.uk> CC: Linus Torvalds , Linux Kernel Mailing List , linux-fsdevel From: Tomi Valkeinen Message-ID: <569C98F7.9010405@ti.com> Date: Mon, 18 Jan 2016 09:49:11 +0200 MIME-Version: 1.0 In-Reply-To: <20160116134458.GK17997@ZenIV.linux.org.uk> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="v9ajruUtq4AdkrSatcRpkWrVCmRIlc5Ti" Sender: linux-fsdevel-owner@vger.kernel.org List-ID: --v9ajruUtq4AdkrSatcRpkWrVCmRIlc5Ti Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 16/01/16 15:44, Al Viro wrote: > FWIW, the main inconvenience with git request-pull is that it still nee= ds > s/gitolite@ra.kernel.org:/git:\/\/git.kernel.org/ postprocessing. It m= imics > the git push, but the remote you are pushing to probably won't be usabl= e for > pulling by others. Looks like it would be useful to have something lik= e > pull_url =3D git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.gi= t > to go with > url =3D gitolite@ra.kernel.org:/pub/scm/linux/kernel/git/viro/vfs.git > in .git/config, settable by something in git remote. OTOH, it's possib= le to > emulate by setting an extra remote and using git push vfs <...> for pus= hes, > while doing git request-pull origin vfs-pull <...> for pull requests...= =20 Isn't "pushurl" for that? I have: [remote "origin"] url =3D git://git.kernel.org/pub/scm/linux/kernel/git/tomba/linux= =2Egit pushurl =3D gitolite.kernel.org:/pub/scm/linux/kernel/git/tomba/l= inux.git fetch =3D +refs/heads/*:refs/remotes/origin/* Tomi --v9ajruUtq4AdkrSatcRpkWrVCmRIlc5Ti Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWnJj3AAoJEPo9qoy8lh71WDgP/3J0pc+Hq5AVWhOz/BnvBzmc 8MJeor0NERvyodr1T+BP99CkIT9V/KTiMw7O5ZOM0OYZkAJ4n8pea/f5ONSIg0Dg v+9XU/lI0uUPCGMhkKW+8HRYnGc/bGTGD41Y1+o+3Iq87T3NelNXiM1NFBcUgYXy h0FhAJIjFgCBOEXLvPEcvSMTwb5MIdr1EMvf8q+g00MmMGcw03o3nhDOGTqcGYU8 tZIPhNO4Ez/k3RVQcoUwYOwI4o9ITL0pq8dOZHtQ99LN4bt/LDCuK2KfnIlY8q7G Hek5Ep2Ah+8boODgdzwa1SyzVGAKG1HNqMCGEJQ9FcZyeRc4q/FecWuyTcWVXyY7 EYsjuvoV43XoukdVQjDY4HMblBRN74xuKkpVjP6wYC9RwpXJ4q/oo+5vbqE/xYYJ 6pGVOzNCuN92kT6HoQcEMUhLmQnWifSuH/jeaSbpf4ejXIt92SSqa0/tQUtSaDlC 4LTCJuvCRqyXHjQxh4USHYQykHEHMBDronHq4vl84hy6s01stqtMijF/tez7q4mm u0KpvzX35d/P3Srq9rA7TU/xP0+MV922mKtbvu75BfCi/uaTJS7/PCAVIVNMG/3y FpYixpHWykjp6M86nr4c+iKAFiV6eQIKckZWlx8IU7Yk5me+BI7LCOEyxwhXMzqw ANKVKixx225jbtLjIveo =rigr -----END PGP SIGNATURE----- --v9ajruUtq4AdkrSatcRpkWrVCmRIlc5Ti--