From: Laurent Vivier <laurent@vivier.eu>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 0/2] M68k for 2.8 patches
Date: Wed, 2 Nov 2016 18:12:06 +0100 [thread overview]
Message-ID: <2d3d33a6-44d4-b2fb-be79-e2f673235719@vivier.eu> (raw)
In-Reply-To: <20161102170707.GB31376@stefanha-x1.localdomain>
[-- Attachment #1: Type: text/plain, Size: 846 bytes --]
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?
Laurent
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-11-02 17:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 9:50 [Qemu-devel] [PULL 0/2] M68k for 2.8 patches Laurent Vivier
2016-10-31 9:50 ` [Qemu-devel] [PULL 1/2] target-m68k: add cmpm Laurent Vivier
2016-10-31 9:50 ` [Qemu-devel] [PULL 2/2] target-m68k: add 64bit mull Laurent Vivier
2016-10-31 13:12 ` [Qemu-devel] [PULL 0/2] M68k for 2.8 patches Laurent Vivier
2016-11-02 17:07 ` Stefan Hajnoczi
2016-11-02 17:12 ` Laurent Vivier [this message]
2016-11-02 17:17 ` Stefan Hajnoczi
2016-11-02 17:23 ` Stefan Hajnoczi
2016-11-02 17:26 ` Laurent Vivier
2016-11-03 16:12 ` Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2d3d33a6-44d4-b2fb-be79-e2f673235719@vivier.eu \
--to=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).