From: Fam Zheng <famz@redhat.com>
To: Maria Kustova <maxa@catit.be>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com,
Maria Kustova <maria.k@catit.be>
Subject: Re: [Qemu-devel] [PATCH V2 2/6] runner: Tool for fuzz tests execution
Date: Thu, 10 Jul 2014 14:03:21 +0800 [thread overview]
Message-ID: <20140710060321.GB5161@T430.redhat.com> (raw)
In-Reply-To: <a049db474b96e6417cf4e19ca1bfce7698e0905b.1404471289.git.maria.k@catit.be>
On Fri, 07/04 15:39, Maria Kustova wrote:
> v1 -> v2:
> Added parameter for a fuzzer configuration file
In the future revisions, please put such revision change notes below a '---'
line, like:
<commit log>
Signed-off-by: Your Name <your@email.com>
---
v1 -> v2: change
This way, it doesn't get into git log when maintainers apply your patch email
with "git am".
The reason is that revision notes only matter when reviewing patches, but has
no value once applied to master.
Thanks,
Fam
next prev parent reply other threads:[~2014-07-10 6:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 11:39 [Qemu-devel] [PATCH V2 0/6] tests: Add the image fuzzer with qcow2 support Maria Kustova
2014-07-04 11:39 ` [Qemu-devel] [PATCH V2 1/6] docs: Specification for the image fuzzer Maria Kustova
2014-07-04 11:39 ` [Qemu-devel] [PATCH V2 2/6] runner: Tool for fuzz tests execution Maria Kustova
2014-07-10 6:03 ` Fam Zheng [this message]
2014-07-04 11:39 ` [Qemu-devel] [PATCH V2 3/6] fuzz: Fuzzing functions for qcow2 images Maria Kustova
2014-07-04 11:39 ` [Qemu-devel] [PATCH V2 4/6] layout: Generator of fuzzed " Maria Kustova
2014-07-10 7:27 ` Fam Zheng
2014-07-04 11:39 ` [Qemu-devel] [PATCH V2 5/6] package: Public API for image-fuzzer/runner/runner.py Maria Kustova
2014-07-04 11:39 ` [Qemu-devel] [PATCH V2 6/6] image-fuzzer: GPLv2 license file Maria Kustova
2014-07-10 6:23 ` Fam Zheng
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=20140710060321.GB5161@T430.redhat.com \
--to=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=maria.k@catit.be \
--cc=maxa@catit.be \
--cc=qemu-devel@nongnu.org \
--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 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).