All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: PRAMOD DEVENDRA <pramod.devendra@citrix.com>
Cc: xen-devel@lists.xenproject.org,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Wei Liu <wei.liu2@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH 1/3] tools/libxl/libxl_qmp.c: Make sure sun_path is NULL terminated in qmp_open
Date: Wed, 18 Mar 2015 10:04:28 +0000	[thread overview]
Message-ID: <1426673068.18247.299.camel@citrix.com> (raw)
In-Reply-To: <1426500338-36798-1-git-send-email-pramod.devendra@citrix.com>

On Mon, 2015-03-16 at 10:05 +0000, PRAMOD DEVENDRA wrote:

Please can you arrange in the future to chain your series into a single
thread. That means that each N/3 mail should have a References and/or
In-reply-to header pointing at either the 0/N mail or the (N-1)/N mail
in the series.

http://wiki.xen.org/wiki/Submitting_Xen_Patches#Sending_the_patches_to_the_list has some information on how to achieve this with git send-email.

Note that this also implies that you should include a 0/N mail which
ties the series together (i.e. explains the overall purpose of the
series). The wiki covers this too.

At the moment my mailbox contains 4 unthread mails from you, named 1/3,
2/3, 3/3 and 2/2 which is liable to get confusing if there are any
further revisions etc.

Ian.

  parent reply	other threads:[~2015-03-18 10:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 10:05 [PATCH 1/3] tools/libxl/libxl_qmp.c: Make sure sun_path is NULL terminated in qmp_open PRAMOD DEVENDRA
2015-03-17 15:42 ` Wei Liu
2015-03-18 10:04 ` Ian Campbell [this message]
2015-03-19  6:40 ` [PATCH v2] libxl/libxl_qmp.c: fix qmp_open PRAMOD DEVENDRA
2015-03-19 10:03   ` Wei Liu
2015-03-19 10:51     ` Ian Campbell
2015-03-19 12:55   ` [PATCH v3] libxl/libxl_qmp.c: fix error handling in qmp_open PRAMOD DEVENDRA
2015-03-20 10:08     ` Wei Liu
2015-03-20 11:56       ` Ian Campbell

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=1426673068.18247.299.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=pramod.devendra@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.