From: "Daniel P. Berrange" <berrange@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-trivial@nongnu.org, thuth@redhat.com,
dgilbert@redhat.com, famz@redhat.com
Subject: Re: [Qemu-devel] [PATCH] tests: Ignore another built executable
Date: Fri, 28 Apr 2017 09:54:07 +0100 [thread overview]
Message-ID: <20170428085407.GC23819@redhat.com> (raw)
In-Reply-To: <20170428022329.30726-1-eblake@redhat.com>
On Thu, Apr 27, 2017 at 09:23:29PM -0500, Eric Blake wrote:
> Commit 78f86a2b7 added a new test, but forgot to exclude the built
> binary from version control.
CC Fam
I wonder if the patchew test system could be made to report an error
if git identifies built files that are not ignored.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-04-28 8:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 2:23 [Qemu-devel] [PATCH] tests: Ignore another built executable Eric Blake
2017-04-28 2:58 ` Thomas Huth
2017-04-28 8:54 ` Daniel P. Berrange [this message]
2017-05-05 6:55 ` Fam Zheng
2017-05-05 6:18 ` Michael Tokarev
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=20170428085407.GC23819@redhat.com \
--to=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=thuth@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 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).