qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [PATCH v2 0/3] following up haiku build fix
@ 2020-06-26 14:00 David CARLIER
  2020-06-29 13:18 ` Stefan Hajnoczi
  0 siblings, 1 reply; 2+ messages in thread
From: David CARLIER @ 2020-06-26 14:00 UTC (permalink / raw)
  To: QEMU Trivial, qemu-devel

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(-)

-- 
2.26.0


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [PATCH v2 0/3] following up haiku build fix
  2020-06-26 14:00 [PATCH v2 0/3] following up haiku build fix David CARLIER
@ 2020-06-29 13:18 ` Stefan Hajnoczi
  0 siblings, 0 replies; 2+ messages in thread
From: Stefan Hajnoczi @ 2020-06-29 13:18 UTC (permalink / raw)
  To: David CARLIER; +Cc: QEMU Trivial, qemu-devel

[-- Attachment #1: Type: text/plain, Size: 1314 bytes --]

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-06-29 13:19 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-06-26 14:00 [PATCH v2 0/3] following up haiku build fix David CARLIER
2020-06-29 13:18 ` Stefan Hajnoczi

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).