qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Kerr <jk@ozlabs.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: patchwork@lists.ozlabs.org, Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: tracking qemu-devel at patchwork.ozlabs.org
Date: Mon, 3 Aug 2009 21:44:52 +1000	[thread overview]
Message-ID: <200908032144.52978.jk@ozlabs.org> (raw)
In-Reply-To: <20090803110944.GA3209@redhat.com>

Michael,

> btw, I wonder why does patchworks sometimes add commas in patch
> subject?

It tries to separate different "bits of information" by commas, and 
normalise spaces into commas:

[PATCH 3/4 v4] -> [3/4,v4]
[PATCH 3/4,v4] -> [3/4,v4]

Since there are spaces in the patch subjects, it thinks that these are 
separate bits of information.

Cheers,


Jeremy

  reply	other threads:[~2009-08-03 11:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29  9:04 [Qemu-devel] tracking qemu-devel at patchwork.ozlabs.org Michael S. Tsirkin
2009-07-29 11:08 ` [Qemu-devel] " Jeremy Kerr
2009-07-29 12:25   ` Michael S. Tsirkin
2009-07-29 13:25     ` Anthony Liguori
2009-07-29 22:52       ` Jeremy Kerr
2009-07-30 12:34         ` Michael S. Tsirkin
2009-07-30 23:41           ` Jeremy Kerr
2009-07-31  0:43             ` Carl-Daniel Hailfinger
2009-07-31  0:58               ` Jeremy Kerr
2009-07-31 13:10             ` Michael S. Tsirkin
2009-08-01  6:15               ` Jeremy Kerr
2009-08-02  6:31                 ` Michael S. Tsirkin
2009-08-02 16:40                   ` Michael S. Tsirkin
2009-08-03 11:09                 ` Michael S. Tsirkin
2009-08-03 11:44                   ` Jeremy Kerr [this message]
2009-08-03 12:21                     ` Michael S. Tsirkin
2012-03-12 20:37   ` [Qemu-devel] " Michael S. Tsirkin
2012-03-13  0:56     ` Jeremy Kerr

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=200908032144.52978.jk@ozlabs.org \
    --to=jk@ozlabs.org \
    --cc=aliguori@us.ibm.com \
    --cc=mst@redhat.com \
    --cc=patchwork@lists.ozlabs.org \
    --cc=qemu-devel@nongnu.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 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).