Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] license.bbclass: hardlink requires write permission
Date: Fri, 19 Dec 2014 15:53:41 +0800	[thread overview]
Message-ID: <5493D985.8010409@windriver.com> (raw)
In-Reply-To: <cover.1415865314.git.liezhi.yang@windriver.com>


Ping.

// Robert

On 11/13/2014 03:55 PM, Robert Yang wrote:
> The following changes since commit e7b731a1a358e0007dba1038ad504888bec5916e:
>
>    docbook-xsl-stylesheets: fix do_configure typo (2014-11-12 15:36:14 +0000)
>
> are available in the git repository at:
>
>    git://git.openembedded.org/openembedded-core-contrib rbt/license
>    http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/license
>
> Robert Yang (1):
>    license.bbclass: hardlink requires write permission
>
>   meta/classes/license.bbclass |    4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
>


      parent reply	other threads:[~2014-12-19  7:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13  7:55 [PATCH 0/1] license.bbclass: hardlink requires write permission Robert Yang
2014-11-13  7:55 ` [PATCH 1/1] " Robert Yang
2014-12-19  7:53 ` Robert Yang [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=5493D985.8010409@windriver.com \
    --to=liezhi.yang@windriver.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