From: Fam Zheng <famz@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] tests: Rename tests/Makefile to tests/Makefile.include
Date: Wed, 15 Jun 2016 08:33:17 +0800 [thread overview]
Message-ID: <20160615003317.GB28081@ad.usersys.redhat.com> (raw)
In-Reply-To: <57607F98.50807@redhat.com>
On Tue, 06/14 16:05, Eric Blake wrote:
> On 05/31/2016 08:23 PM, Fam Zheng wrote:
> > The file is only included from the top Makefile. Rename it to reflect
> > this more obviously.
> >
> > Signed-off-by: Fam Zheng <famz@redhat.com>
> > ---
> > Makefile | 2 +-
> > tests/{Makefile => Makefile.include} | 0
> > 2 files changed, 1 insertion(+), 1 deletion(-)
> > rename tests/{Makefile => Makefile.include} (100%)
>
> Reviewed-by: Eric Blake <eblake@redhat.com>
This one is already applied in master.
Fam
next prev parent reply other threads:[~2016-06-15 0:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 2:23 [Qemu-devel] [PATCH] tests: Rename tests/Makefile to tests/Makefile.include Fam Zheng
2016-06-14 22:05 ` Eric Blake
2016-06-15 0:33 ` Fam Zheng [this message]
2016-06-15 1:41 ` 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=20160615003317.GB28081@ad.usersys.redhat.com \
--to=famz@redhat.com \
--cc=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).