From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46266) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c1zIw-0006gR-NO for qemu-devel@nongnu.org; Wed, 02 Nov 2016 13:26:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c1zIt-0004SW-Jw for qemu-devel@nongnu.org; Wed, 02 Nov 2016 13:26:26 -0400 Received: from mout.kundenserver.de ([212.227.126.130]:56012) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1c1zIt-0004Ry-A1 for qemu-devel@nongnu.org; Wed, 02 Nov 2016 13:26:23 -0400 References: <1477907431-10008-1-git-send-email-laurent@vivier.eu> <20161102170707.GB31376@stefanha-x1.localdomain> <2d3d33a6-44d4-b2fb-be79-e2f673235719@vivier.eu> From: Laurent Vivier Message-ID: <2f05ca9f-49c5-b29b-7367-dd8fae48df6a@vivier.eu> Date: Wed, 2 Nov 2016 18:26:20 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] [PULL 0/2] M68k for 2.8 patches List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: qemu-devel Le 02/11/2016 à 18:23, Stefan Hajnoczi a écrit : > On Wed, Nov 2, 2016 at 5:17 PM, Stefan Hajnoczi wrote: >> On Wed, Nov 2, 2016 at 5:12 PM, Laurent Vivier wrote: >>> Le 02/11/2016 à 18:07, Stefan Hajnoczi a écrit : >>>> On Mon, Oct 31, 2016 at 10:50:29AM +0100, Laurent Vivier wrote: >>>>> The following changes since commit 5b2ecabaeabc17f032197246c4846b9ba95ba8a6: >>>>> >>>>> Merge remote-tracking branch 'remotes/kraxel/tags/pull-ui-20161028-1' into staging (2016-10-28 17:59:04 +0100) >>>>> >>>>> are available in the git repository at: >>>>> >>>>> git@github.com:vivier/qemu-m68k.git tags/m68k-for-2.8-pull-request >>>> >>>> This URI is not publicly accessible. Some tools will fail to apply your >>>> pull request because of this. >>>> >>>> Please adjust your .gitconfig: >>>> >>>> [remote "origin"] >>>> url = git://github.com/vivier/qemu.git >>>> pushurl = git@github.com:vivier/qemu.git >>> >>> Thank you Stefan. >>> >>> I'm using your tool "git-publish", is there a way to detect this problem >>> automatically? >> >> Right now git-publish doesn't check the generated URI. In some use >> cases it's reasonable to use an SSH URI so adding an error or even >> warning to git-publish isn't ideal. >> >> I am modifying the patches tool (https://github.com/stefanha/patches) >> to automatically translate GitHub URIs since they are so prevalent... >> This will allow me to apply pull requests that have GitHub SSH URIs. > > On second thought, even that isn't a general solution. If people are > collaborating on private GitHub repos then translating URIs to HTTPS > is not correct either. > > Instead of trying to do magic I'll ask pull request submitters to fix > their .gitconfig. Perhaps you can also update git-publish README.rst? Thanks, Laurent