From: Robert Yang <liezhi.yang@windriver.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2] bitbake.conf: add GITHUB_GIT
Date: Wed, 29 Jul 2015 18:19:06 +0800 [thread overview]
Message-ID: <55B8A89A.6050406@windriver.com> (raw)
In-Reply-To: <5755146.lYtmNt1cvb@peggleto-mobl.ger.corp.intel.com>
On 07/29/2015 06:11 PM, Paul Eggleton wrote:
> Hi Robert,
>
> On Wednesday 29 July 2015 02:11:53 Robert Yang wrote:
>> The following changes since commit 27d068d05239c26a3848eb101571acab54635e37:
>>
>> harfbuzz: upgrade to 1.0.1 (2015-07-27 23:28:23 +0100)
>>
>> are available in the git repository at:
>>
>> git://git.openembedded.org/openembedded-core-contrib rbt/github
>>
>> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/
>> github
>>
>> Robert Yang (2):
>> bitbake.conf: add GITHUB_GIT
>> meta: git://github.com -> ${GITHUB_GIT}
>
> Interesting, but you don't explain why this change is needed in the commit
> messages.
Hi Paul,
It is just like what GNOME_GIT, GNU_MIRROR and others did.
// Robert
>
> Cheers,
> Paul
>
next prev parent reply other threads:[~2015-07-29 10:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 9:11 [PATCH 0/2] bitbake.conf: add GITHUB_GIT Robert Yang
2015-07-29 9:11 ` [PATCH 1/2] " Robert Yang
2015-07-29 9:11 ` [PATCH 2/2] meta: git://github.com -> ${GITHUB_GIT} Robert Yang
2015-07-29 10:11 ` [PATCH 0/2] bitbake.conf: add GITHUB_GIT Paul Eggleton
2015-07-29 10:19 ` Robert Yang [this message]
2015-07-29 11:48 ` Olof Johansson
2015-07-29 16:27 ` Otavio Salvador
2015-07-30 1:51 ` Robert Yang
2015-07-30 7:04 ` Olof Johansson
2015-07-30 7:09 ` Robert Yang
2015-07-30 8:32 ` Olof Johansson
2015-07-30 11:34 ` Otavio Salvador
2015-07-31 14:30 ` Richard Purdie
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=55B8A89A.6050406@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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.