On Fri, Jun 26, 2020 at 03:00:57PM +0100, David CARLIER wrote:
> From 6fa7a4108236f513201192654e07c7044a3d7e58 Mon Sep 17 00:00:00 2001
> From: David Carlier <devnexen@gmail.com>
> Date: Fri, 26 Jun 2020 14:48:28 +0000
> Subject: [PATCH 0/3] following up haiku build fix
>
> David Carlier (3):
> check sys/signal.h presence
> define SIGIO for haiku
> qemu_init_exec_dir Haiku implementation
>
> configure | 8 ++++++++
> hw/xen/xen-legacy-backend.c | 1 -
> include/qemu/osdep.h | 6 +++++-
> util/oslib-posix.c | 20 +++++++++++++++++++-
> 4 files changed, 32 insertions(+), 3 deletions(-)
Please send multi-patch series as an email thread. Using email threads
make it easier for humans to apply all emails, mark them as read, or
delete them in mail clients. Continuous integration scripts may also
rely on email threading to identify patch series.
A patch series email thread looks like this:
[PATCH 0/N] Cover letter
+-- [PATCH 1/N] First patch
+-- [PATCH 2/N] Second patch
...
+-- [PATCH N/N] Last patch
The In-Reply-To and References email headers control threading. See the
git-send-email(1) --thread option (it's enabled by default so either
your gitconfig or command-line have disabled it).
Thanks,
Stefan