From: Robert Yang <liezhi.yang@windriver.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: About subversion_1.8.10.bb and subversion_1.6.15.bb
Date: Wed, 28 Jan 2015 09:07:20 +0800 [thread overview]
Message-ID: <54C83648.1060907@windriver.com> (raw)
In-Reply-To: <20150127151830.GA2477@jama>
On 01/27/2015 11:18 PM, Martin Jansa wrote:
> On Tue, Jan 27, 2015 at 05:26:37PM +0800, Robert Yang wrote:
>>
>> We have both subversion_1.8.10.bb and subversion_1.6.15.bb in oe-core
>> layer, and their license are the same (Apache-2), does anyone know why
>> we need keep subversion_1.6.15.bb, please ? I'd like to remove the old
>> one if no objections.
>
> Different checkout format.
Thanks, so I think that we need keep subversion_1.6.15.bb ?
// Robert
>
prev parent reply other threads:[~2015-01-28 1:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 9:26 About subversion_1.8.10.bb and subversion_1.6.15.bb Robert Yang
2015-01-27 15:18 ` Martin Jansa
2015-01-28 1:07 ` 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=54C83648.1060907@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=martin.jansa@gmail.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