From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] tests: Ignore test-blockjob-txn
Date: Fri, 13 Nov 2015 07:55:29 -0700 [thread overview]
Message-ID: <5645F9E1.6070108@redhat.com> (raw)
In-Reply-To: <20151113102603.GH6650@stefanha-x1.localdomain>
[-- Attachment #1: Type: text/plain, Size: 801 bytes --]
On 11/13/2015 03:26 AM, Stefan Hajnoczi wrote:
> On Thu, Nov 12, 2015 at 11:33:48AM -0700, Eric Blake wrote:
>> Commit 6c6f312d added a new test, but did not mark it for
>> exclusion in .gitignore.
>>
>> Signed-off-by: Eric Blake <eblake@redhat.com>
>> ---
>>
>> Yeah, I know this affects only non-VPATH builds, which we don't
>> recommend, but we might as well be consistent.
>
> I'm a non-VPATH diehard too :)
>
>> tests/.gitignore | 1 +
>> 1 file changed, 1 insertion(+)
>
> Thanks, applied to my block tree:
> https://github.com/stefanha/qemu/commits/block
Did you want to apply v2 instead?
https://lists.gnu.org/archive/html/qemu-devel/2015-11/msg03214.html
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] tests: Ignore test-blockjob-txn
Date: Fri, 13 Nov 2015 07:55:29 -0700 [thread overview]
Message-ID: <5645F9E1.6070108@redhat.com> (raw)
In-Reply-To: <20151113102603.GH6650@stefanha-x1.localdomain>
[-- Attachment #1: Type: text/plain, Size: 801 bytes --]
On 11/13/2015 03:26 AM, Stefan Hajnoczi wrote:
> On Thu, Nov 12, 2015 at 11:33:48AM -0700, Eric Blake wrote:
>> Commit 6c6f312d added a new test, but did not mark it for
>> exclusion in .gitignore.
>>
>> Signed-off-by: Eric Blake <eblake@redhat.com>
>> ---
>>
>> Yeah, I know this affects only non-VPATH builds, which we don't
>> recommend, but we might as well be consistent.
>
> I'm a non-VPATH diehard too :)
>
>> tests/.gitignore | 1 +
>> 1 file changed, 1 insertion(+)
>
> Thanks, applied to my block tree:
> https://github.com/stefanha/qemu/commits/block
Did you want to apply v2 instead?
https://lists.gnu.org/archive/html/qemu-devel/2015-11/msg03214.html
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-11-13 14:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 18:33 [Qemu-trivial] [PATCH] tests: Ignore test-blockjob-txn Eric Blake
2015-11-12 18:33 ` [Qemu-devel] " Eric Blake
2015-11-13 2:27 ` [Qemu-trivial] " Stefan Hajnoczi
2015-11-13 2:27 ` [Qemu-devel] " Stefan Hajnoczi
2015-11-13 3:43 ` [Qemu-trivial] " Eric Blake
2015-11-13 3:43 ` [Qemu-devel] " Eric Blake
2015-11-13 10:26 ` [Qemu-trivial] " Stefan Hajnoczi
2015-11-13 10:26 ` Stefan Hajnoczi
2015-11-13 14:55 ` Eric Blake [this message]
2015-11-13 14:55 ` Eric Blake
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=5645F9E1.6070108@redhat.com \
--to=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.