All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Yang <richardw.yang@linux.intel.com>
To: qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Cc: mjt@tls.msk.ru, imammedo@redhat.com,
	Wei Yang <richardw.yang@linux.intel.com>
Subject: [Qemu-trivial] [PATCH 0/2] CODING_STYLE: trivial update
Date: Tue, 19 Feb 2019 09:31:04 +0800	[thread overview]
Message-ID: <20190219013106.17538-1-richardw.yang@linux.intel.com> (raw)

The first one is suggested by Igor Mammedov to provide rule for multiline
code.

The second is a trivial fix to make example code all indented with 4 spaces.

Wei Yang (2):
  CODING_STYLE: specify the indent rule for multiline code
  CODING_STYLE: indent example code as all others

 CODING_STYLE | 34 ++++++++++++++++++++++++++++++----
 1 file changed, 30 insertions(+), 4 deletions(-)

-- 
2.19.1



WARNING: multiple messages have this Message-ID (diff)
From: Wei Yang <richardw.yang@linux.intel.com>
To: qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Cc: mjt@tls.msk.ru, imammedo@redhat.com,
	Wei Yang <richardw.yang@linux.intel.com>
Subject: [Qemu-devel] [PATCH 0/2] CODING_STYLE: trivial update
Date: Tue, 19 Feb 2019 09:31:04 +0800	[thread overview]
Message-ID: <20190219013106.17538-1-richardw.yang@linux.intel.com> (raw)

The first one is suggested by Igor Mammedov to provide rule for multiline
code.

The second is a trivial fix to make example code all indented with 4 spaces.

Wei Yang (2):
  CODING_STYLE: specify the indent rule for multiline code
  CODING_STYLE: indent example code as all others

 CODING_STYLE | 34 ++++++++++++++++++++++++++++++----
 1 file changed, 30 insertions(+), 4 deletions(-)

-- 
2.19.1

             reply	other threads:[~2019-02-19  1:33 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19  1:31 Wei Yang [this message]
2019-02-19  1:31 ` [Qemu-devel] [PATCH 0/2] CODING_STYLE: trivial update Wei Yang
2019-02-19  1:31 ` [Qemu-trivial] [PATCH 1/2] CODING_STYLE: specify the indent rule for multiline code Wei Yang
2019-02-19  1:31   ` [Qemu-devel] " Wei Yang
2019-02-19 17:34   ` [Qemu-trivial] " Philippe Mathieu-Daudé
2019-02-19 17:34     ` Philippe Mathieu-Daudé
2019-02-19 17:55     ` [Qemu-trivial] " Eric Blake
2019-02-19 17:55       ` Eric Blake
2019-02-19 22:03       ` [Qemu-trivial] " Wei Yang
2019-02-19 22:03         ` Wei Yang
2019-02-19 17:52   ` [Qemu-trivial] " Eric Blake
2019-02-19 17:52     ` Eric Blake
2019-02-19 22:04     ` [Qemu-trivial] " Wei Yang
2019-02-19 22:04       ` Wei Yang
2019-02-19  1:31 ` [Qemu-trivial] [PATCH 2/2] CODING_STYLE: indent example code as all others Wei Yang
2019-02-19  1:31   ` [Qemu-devel] " Wei Yang
2019-02-19 17:38   ` [Qemu-trivial] " Philippe Mathieu-Daudé
2019-02-19 17:38     ` Philippe Mathieu-Daudé
2019-02-19 17:56     ` [Qemu-trivial] " Eric Blake
2019-02-19 17:56       ` Eric Blake
2019-02-19 18:55       ` [Qemu-trivial] " Philippe Mathieu-Daudé
2019-02-19 18:55         ` Philippe Mathieu-Daudé
2019-02-19 22:20         ` [Qemu-trivial] " Wei Yang
2019-02-19 22:20           ` Wei Yang
2019-02-19 23:55           ` [Qemu-trivial] " Philippe Mathieu-Daudé
2019-02-19 23:55             ` Philippe Mathieu-Daudé
2019-02-19 22:05     ` [Qemu-trivial] " Wei Yang
2019-02-19 22:05       ` Wei Yang
2019-02-19 17:57   ` [Qemu-trivial] " Eric Blake
2019-02-19 17:57     ` Eric Blake

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=20190219013106.17538-1-richardw.yang@linux.intel.com \
    --to=richardw.yang@linux.intel.com \
    --cc=imammedo@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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 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.