public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Randle, William C" <william.c.randle@intel.com>
To: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	"daicy.fnst@cn.fujitsu.com" <daicy.fnst@cn.fujitsu.com>
Subject: Re: [PATCH] dbus: 1.10.8 -> 1.11.2
Date: Wed, 17 Aug 2016 15:19:45 +0000	[thread overview]
Message-ID: <1471447185.2860.53.camel@intel.com> (raw)
In-Reply-To: <1461850657-5088-1-git-send-email-daicy.fnst@cn.fujitsu.com>

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

On Thu, 2016-04-28 at 16:37 +0300, Dai Caiyun wrote:

Upgrade dbus from 1.10.8 to 1.11.2.




You might want to update the date/time of the machine you used to post your patches. With a date of April 28, your email could easily be missed by someone sorting and reading messages by date.

    -Bill

[-- Attachment #2: Type: text/html, Size: 623 bytes --]

      parent reply	other threads:[~2016-08-17 15:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-17  6:26 [PATCH] dbus: 1.10.8 -> 1.11.2 Dai Caiyun
2016-08-17  7:36 ` Jussi Kukkonen
2016-08-17 15:19 ` Randle, William C [this message]

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=1471447185.2860.53.camel@intel.com \
    --to=william.c.randle@intel.com \
    --cc=daicy.fnst@cn.fujitsu.com \
    --cc=openembedded-core@lists.openembedded.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